Re: [Savannah-hackers] submission of ONG : ONQ AND OTHERS - savannah.nongnu.org

[Sylvain Beucler]

Hi,

Sorry for the delay,

On Tue, Sep 07, 2004 at 09:03:23PM +0100, Ozan Türkyilmaz wrote:
>  --- Sylvain Beucler <address@hidden> wrote: 
> > Hi,
> > 
> > On Mon, Sep 06, 2004 at 08:37:16AM +0100, Ozan
> > Türkyilmaz wrote:
> > > i am sending you updated version of source code
> > for
> > > you 
> > 
> > parser.c has an incomplete license header: it refers
> > to a file named
> > 'LICENSE' that is not present in the distribution.
> > Hence I cannot know
> > under what license it is released. You should add
> > the LICENSE file in
> > your archive. You can renamed it and change the
> > license notice
> > accordingly if needed.
> > 
> what about now ?

Unfortunately, no :/


First, the file 'parser.c' from aewm was not released under the GNU
GPL. Its license says:

"The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software."

You only let the original header and added a file LICENSE containing
the GNU GPL. Since the file is not released under the GNU GPL, this is
not fine.

I recommand that you rewrite the permission notices from lib/* so that
they comply with the original license: copy the orignal copyright and
the notice from aewm's license, and hence remove the references to
aewm's LICENSE file. You therefore do not have to copy aewm's LICENSE
file in your archive.

Then you rename your "LICENSE" file to a more standard "COPYING" file,
and use again standard license notices in your code, because the one
you now use are now incomplete. The notices in your previous tarball
were ok.

Please follow these instructions:

"In order to release your project properly and unambiguously 
under the GPL, please place copyright notices and permission-to-copy
statements at the beginning of every file of source code.

In addition, if you haven't already, please copy a copy of the plain
text version of the GPL, available from
(http://www.gnu.org/licenses/gpl.txt), into a file named "COPYING".

Additional instructions are available from
http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.  To learn
why a copy of the GPL must be included with every copy of the code,
for example, go to
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude";

-- 
Sylvain