On Wed, Jun 04, 2003 at 07:38:10PM -0400, [EMAIL PROTECTED] wrote: > > A package was submitted to savannah.nongnu.org > This mail was sent to [EMAIL PROTECTED], [EMAIL PROTECTED] > > > Aaron D. Ball <[EMAIL PROTECTED]> described the package as follows: > License: gpl > Other License: > Package: The Enki Document Server > System name: enki > Type: non-GNU > > Description: > The software is currently just a simple web server, responding in HTTP/1.1 to GET > and HEAD requests for static documents. In the future, it will permit authorized > users to introduce new documents (optionally relating them to existing documents), > offer interfaces via other protocols (particularly SMTP and IMAP), and generally > unite the essentially similar functions of weblogs, mailing lists, Usenet, web pages > with comment facilities, and other forms of threaded communication. > > The software is written in Ruby, which provides powerful programming abstractions > and standard libraries that together make it possible to write code that is both > compact and legible. I believe that this, combined with careful modularization and > delegation to the host operating system, will lead to software that is unusually > maintainable, reliable, and secure. > > http://enki.net/ > > is a tiny web site running the current version of the software, whose source code is > at > > http://enki.net/Writing/Ruby/DocumentServer
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, Rudy > > for the time being. > > > Other Software Required: > The software is written in Ruby and relies on Ruby\'s rich set of standard > libraries, which are licensed as described at > > http://www.ruby-lang.org/en/LICENSE.txt > > which explicitly permits licensing either under the GPL or under a different free > software license specific to Ruby. At present, I do not anticipate adding further > third-party libraries; my intention is to keep the software simple when I can, but > create my own complexity when I must. > > > Other Comments: > > > > > _______________________________________________ > Savannah-hackers mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/savannah-hackers -- 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
