#6491: [with spkg, positive review pending] Modular Cohomology Rings of Finite
p-Groups
-------------------------------+--------------------------------------------
 Reporter:  SimonKing          |       Owner:  SimonKing                     
     Type:  enhancement        |      Status:  assigned                      
 Priority:  major              |   Milestone:  sage-4.1.1                    
Component:  optional packages  |    Keywords:  cohomology ring finite p-group
 Reviewer:                     |      Author:  Simon King                    
   Merged:                     |  
-------------------------------+--------------------------------------------

Comment(by wdj):

 Replying to [comment:26 SimonKing]:
 > There's news about licences:
 >
 > Michael Ringe kindly agreed to provide mtx-2.2.3 with a new licence "GPL
 v2 or later", hence, he put a version mtx-2.2.4 on the download page, and
 as much as I see it differs from mtx-2.2.3 only by a new COPYING file.
 >


 Good news!


 > So, I guess that in the documentation of our package I should replace
 all references to mtx-2.2.3 by a reference to mtx-2.2.4, and I should
 provide the new original sources in the folder 'mtxoriginal/' of our
 package.
 >
 > My questions:
 >  - Look at the folder 'src/mtx-2.2.3'. Does it suffice to rename that
 folder to 'src/mtx-2.2.4' and replace the old COPYING file by the new one?


 That seems fine.


 >  - Specifically: Is it a problem that we use files showing cvs (or svn?)
 numbers that are different from those on the MeatAxe download page? For
 example, the


 I don't see how this is a problem.


 > ''official''  'zzz.c' from the download page starts with
 >    {{{
 > /* ========================== C MeatAxe =============================
 >    Finite field arithmetic and common functions. `Small' version for
 >    field orders q <= 256. Originally based on the `hprout.c' written
 >    by Klaus Lux.
 >
 >    (C) Copyright 1993 Michael Ringe, Lehrstuhl D fuer Mathematik,
 >    RWTH Aachen, Germany  <[email protected]>
 >    This program is free software; see the file COPYING for details.
 >    ================================================================== */
 >
 >
 > /* $Id: zzz.c,v 2.20 1995/06/22 13:19:45 mringe Exp $
 >  *
 >  * $Log: zzz.c,v $
 >  * Revision 2.20  1995/06/22  13:19:45  mringe
 >  * Teste, ob MeatAxeBinDir != 0
 >  *
 >  * Revision 2.19  1995/05/12  10:07:20  mringe
 >  * Benutze MeatAxeBinDir beim Aufruf von maketab.
 >  *
 >  * Revision 2.18  1994/11/28  16:38:00  mringe
 >  * Neue Namen: SFOpen() und SFSeek().
 >  *
 >    }}}
 >    while we have the corresponding file starting with
 >    {{{
 > /* ========================== C MeatAxe =============================
 >    Finite field arithmetic and common functions. `Small' version for
 >    field orders q <= 256. Originally based on the `hprout.c' written
 >    by Klaus Lux.
 >
 >    (C) Copyright 1993 Michael Ringe, Lehrstuhl D fuer Mathematik,
 >    RWTH Aachen, Germany  <[email protected]>
 >    This program is free software; see the file COPYING for details.
 >    ================================================================== */
 >
 >
 > /* $Id: zzz.c,v 1.2 1997/09/11 15:44:42 gap Exp $
 >  *
 >  * $Log: zzz.c,v $
 >  * Revision 1.2  1997/09/11 15:44:42  gap
 >  * New version 2.2.3. AH
 >  *
 >  * Revision 2.20  1995/06/22  13:19:45  mringe
 >  * Teste, ob MeatAxeBinDir != 0
 >  *
 >  * Revision 2.19  1995/05/12  10:07:20  mringe
 >  * Benutze MeatAxeBinDir beim Aufruf von maketab.
 >    }}}
 >
 >    So, my question is: Must these file headers match in order to conform
 with the licence? If this were the case, I had a lot of dull work to do...
 >
 >  - My files start with a header such as
 >    {{{
 >
 #*****************************************************************************
 > #
 > #    Cohomology Rings of Finite p-Groups
 > #
 > #    Copyright (C) 2009 Simon A. King <[email protected]>
 > #
 > #  Distributed under the terms of the GNU General Public License (GPL)
 > #
 > #    This code 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.
 > #
 > #  The full text of the GPL is available at:
 > #
 > #                  http://www.gnu.org/licenses/
 >
 #*****************************************************************************
 >    }}}
 >    Does this already mean that my code is ''correctly'' (whatever that
 means) licenced under GPL? Or do I need to provide a COPYING file as well?


 You should change "#  Distributed under the terms of the GNU General
 Public License (GPL)" to "#  Distributed under the terms of the GNU
 General Public License (GPL), version 2 or later (at your choice)" or
 something like that.

 If you don't specify the version of the GPL you use then it defaults to
 the latest version (which is version 3 currently). You don't want that.


 >
 > Please excuse if these questions are stupid. But my impression is that
 licences are taken serious, and I have ''no idea whatsoever'' on that
 matter.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6491#comment:27>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to