Hi, I'm evaluating the project you submitted for approval in Savannah.
[EMAIL PROTECTED] said: > A package was submitted to savannah.nongnu.org > This mail was sent to [EMAIL PROTECTED], [EMAIL PROTECTED] > > Maciej Paczesny <[EMAIL PROTECTED]> described the package as follows: > License: gpl > Other License: > Package: Polish News Module > System name: pnm > Type: non-GNU > > Description: > Polish News Module is a project of a module to be used in SuperKaramba > (http://netdragon.sourceforge.net/) tool. > PNM's intention is to bring the SuperKaramba user as much news from any RDF/RSS > supported sites as possible. > It consists of an engine written in Python language to make the news appear on the > KDE desktop, and of a set of plugins with logos (png) and scripts (Perl/Python) > needed to download the news. > Currently there are 2 people involved in this project, but we are receiving a lot of > code suggestions from other PNM users. > Our idea to register this project on Savannah.gnu.org is to let other > people/developers take a part in the construction of future releases, and to give > the users a possibility to report a bug and to solve some bug-related problem. > The PNM currently is hosted on kdelook.org > (http://www.kdelook.org/content/show.php?content=6186) > The package source is at http://www.kdelook.org/content/download.php?content=6186 > 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 _______________________________________________ Savannah-hackers mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/savannah-hackers
