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] > > RM <[EMAIL PROTECTED]> described the package as follows: > License: gpl > Other License: > Package: ventura > System name: ventura > Type: non-GNU > > Description: > Ventura is a php/mysql based blog software that is simple to use for both writers > and readers. It allows for easy entry and editing. It also allows for image > uploading and viewing. The interface is calendar based for easy operation. > > the software can be seen in action here: > > http://blog.ventura.nu > > Source code can be downloaded here: > > http://gmconsult.com/ventura-0.2.tgz > > The source is completely written by me except one calendar function that is freeware > and contains no restrictions as long as the copyright notice remains in place. > > Other Software Required: > > Other Comments: > Currently, i have no license information written within the source files nor within > the source directory. my question to you: what is the best way to go about that? 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