phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [phpGroupWare-developers] Licensing


From: Dave Hall
Subject: Re: [phpGroupWare-developers] Licensing
Date: Sun, 28 Jan 2007 20:25:37 +1100

Hi Sigurd,

On Fri, 2007-01-26 at 15:06 +0100, Sigurd Nes wrote:
> Hi
> Is phpgroupware licensed as GPL - or LGPL ?
> 

As mentioned by Chris, GPL, parts of the API are LGPL (or use other GPL
compatible licenses).

> Some license-info seems to be missing from our headers
> see:  http://www.gnu.org/licenses/gpl-howto.html

That is a suggestion from the FSF, it isn't mandatory.  There are
reasons why it should be more detailed that what they are today.

For classes I think we should be using something like this

<?php
        /**
         * Short description of the class
         *
         * @author Name <address@hidden>
         * @copyright Copyright (C) 2000-2007 Free Software Foundation, Inc. 
http://www.fsf.org/
         * @license http://www.gnu.org/licenses/gpl.html GNU General Public 
License
         * @package appname
         * @subpackage optional
         * @version $Id$
         */

        /*
        This file is part of phpGroupWare - appname.
        
        Foobar is free software; you can redistribute it and/or modify
        it under the terms of the GNU General Public License as published by
        the Free Software Foundation; either version 2 of the License, or
        (at your option) any later version.

        phpGroupWare - appname is distributed in the hope that it will be 
        useful, but WITHOUT ANY WARRANTY; without even the implied warranty 
        of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
        GNU General Public License for more details.

        You should have received a copy of the GNU General Public License
        along with Foobar; if not, write to the Free Software
        Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  
USA
        */

        /**
         * Short description of the class
         *
         * @package appname
         * @subpackage optional
         */
        class class_name
        {
        }
?>

That way we have the PHPdocs and have the text the FSF prefers.  That
should keep everyone happy.

Quick history less, when Kai added the phpdoc headers the longer FSF
text was dropped from the headers.  Then when there were problems with
the headers he left the project.

Cheers

Dave
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
e address@hidden
w phpgroupware.org
j address@hidden
sip address@hidden
       _            ____                    __        __             
 _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___ 
| '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
| |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
| .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
|_|         |_|                         |_|Web based collaboration platform






reply via email to

[Prev in Thread] Current Thread [Next in Thread]