[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers] Re: submission of Morse Code Tool - savannah.nongnu.o
From: |
Mathieu Roy |
Subject: |
[Savannah-hackers] Re: submission of Morse Code Tool - savannah.nongnu.org |
Date: |
15 Jul 2003 13:25:42 +0200 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Hi,
I'm evaluating the project you submitted for approval in Savannah.
address@hidden said:
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
>
> Oliver F. M. Stoll <address@hidden> described the package as follows:
> License: gpl
> Other License:
> Package: Morse Code Tool
> System name: mct
> Type: non-GNU
>
> Description:
> Morse code trainer (mct) is a small utility written in C++,
> that takes a certain set of characters (letters, numbers and
> some special characters) as input, and outputs the corresponding
> morse code on /dev/dsp with specifiable speed and pitch.
>
> An additional utility (mctmkcode) generates columns of random
> text to pipe into "mct" for practice.
>
> The software should run on any system with GNU-C++ compiler and
> a working DSP device.
>
> A first version can be seen at http://ofmstoll.de/bin/mct-linux-1.0.tar.gz
To release your project under the GPL, you should put
copyright notices and copying permission statements
at the beginning of every source-code file, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt).
Put it in a file named COPYING.
Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html.
The GPL FAQ explain the reason behind these recommendations. For
example, there is an entry explaining why the GPL requires including a
copy of the GPL with every copy of the program:
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude
Please register your project once more with the changes mentioned
above. The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times. Thank you for your
understanding.
Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.
Regards,
--
Mathieu Roy
Homepage:
http://yeupou.coleumes.org
Not a native english speaker:
http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english