savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Project Approval [logs]


From: Michael J. Flickinger
Subject: [Savannah-hackers] Project Approval [logs]
Date: Mon, 23 Aug 2004 02:40:56 -0400
User-agent: KMail/1.5.3

Hi,

I'm evaluating the project you submitted for approval in Savannah.

On Thu, 5 Aug 2004 06:56:09 -0600 (MDT), Jim Prewett <address@hidden> 
wrote:
> 
> I'm not sure why, but it seems odd to me that i'm getting this mail (I too
> applied for a Savannah account to host my project).
> 
> Is Savannah back up and running?  When should I expect to be informed of
> the status of my new project on Savannah?
> 
> Thanks,
> Jim

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

The following files lack the required GPL header:

        ./data_structures/doubly-linked-list.lsp
        ./data_structures/priority-queue.lsp
        ./data_structures/queue.lsp
        ./apachehelp.lsp
        ./collection.lsp
        ./context.lsp
        ./davesrules.lsp
        ./myrules.lsp
        ./regexp-create.lsp
        ./regexps.lsp
        ./rule.lsp
        ./ruleset.lsp
        ./sysloghelp.lsp
        ./tail.lsp

If you are willing to make the changes mentioned above, please provide
us with an URL to an updated tarball of your project.  Upon review, we
will reconsider your project for inclusion in Savannah.

Regards,


-- 
Michael J. Flickinger





reply via email to

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