On Saturday 27 October 2007 08:25:57 Paul Cochrane via RT wrote: > languages/regex/lib/Regex/Grammar.pm: > (c) Copyright 1998-2001 Francois Desarmenien, all rights reserved. > > This file is automatically generated. So what do we do with files in > such cases? It is generated from Parse::Yapp, so can we just generate > this file on demand rather than have it committed to the repository?
We can do that only if we mark Parse::Yapp as a dependency that people need to have installed if they want to work on the file. (We take the opposite approach for lex and yacc). If Francois really claims all rights over that file, we have no right to distribute it however... so we might be in violation of his copyright. > compilers/imcc/imcc.y, compilers/imcc/main.c, compilers/imcc/ > parser_util.c, > languages/cola/: > Copyright (C) 2002 Melvin Smith <[EMAIL PROTECTED]> > > Much of Melvin's stuff is co-licensed with The Perl Foundation, so can > we safely assume that the copyright here can just be updated to > Artistic 2.0? We should ask Melvin about the license and any change thereof. > > languages/urm/examples/biggerzero.urm:3 > > languages/urm/examples/distance.urm:3 > > languages/urm/examples/div.urm:3 > > languages/urm/examples/mult.urm:3 > > languages/urm/examples/sim.urm:3 > > languages/urm/examples/sub.urm:3 > > languages/urm/README:137 > > languages/urm/t/syn.t:13 > > languages/urm/urmc:11 > > This language is all GPLd, so maybe a good canditate for being moved to > google-code. Or perhaps we could ask the author if we can license it > under Artistic 2.0? Opinions? Let's start by asking the author. I don't see any particular problem with including GPLd code in the repository under languages/ (it seems like aggregation to me), except that anyone who copies code verbatim into another project may trigger the redistribution clause of the GPL. -- c
