Hi, I'm evaluating the project you submitted for approval in Savannah.
On Wed, Aug 20, 2003 at 06:15:07PM -0400, [EMAIL PROTECTED] wrote: > > A package was submitted to savannah.gnu.org > This mail was sent to [EMAIL PROTECTED], [EMAIL PROTECTED] > > > Pupeno <[EMAIL PROTECTED]> described the package as follows: > License: gpl The license does not contain the last section, titled "How to Apply These Terms to Your New Programs". Please use a complete verbatim copy of the license, which may be found at http://www.gnu.org/licenses/gpl.txt, http://www.gnu.org/licenses/lgpl.txt or http://www.gnu.org/licenses/fdl.txt The license must be copied verbatim and in its entirety. > Other License: > Package: Music Learning Suite > System name: mls > Type: non-GNU > > Description: > Musical Learning Suite is a set of programs to help people learn music and improve > musical skills. > It will contain several modules, now on development Score Reading Trainer that helps > people improve the speed and accuracy of reading musical scores. > There are several other modules planned: > Rythmical training. Melodic training. Ear training. > I'd like to send the current sources (not much) by mail. > > Other Software Required: > It dependes on KDE/Qt mainly. No other dependencies yet but some may be added to > handle Midi ports and so on. > 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 Some files have it right, others haven't. (Also the cpp template is done wrong). Please register your project once more with the changes mentioned above. We cannot track projects that have been answered but not approved, so we must ask you to register the project whenever you change the registration. Make sure to apply all changes so you need to reregister only once. The re-registration URL found in our acknowledgement of your earlier registration will direct you to the proper location. You can mail the updated tarball to me again. Regards, Rudy -- Rudy Gevaert [EMAIL PROTECTED] Web page http://www.webworm.org GNU/Linux for schools http://www.nongnu.org/glms Savannah hacker http://savannah.gnu.org _______________________________________________ Savannah-hackers mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/savannah-hackers
