[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #13308] Submission of SlashNerd

From: taj
Subject: [Savannah-register-public] [task #13308] Submission of SlashNerd
Date: Wed, 17 Sep 2014 23:52:25 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20140319 Firefox/24.0 Iceweasel/24.4.0

Follow-up Comment #14, task #13308 (project administration):

UPDATE: I finised the re-write (and test && commit) of Slash::Password,
copyright and license information (GPLv2) is included.

I have some questions about the remainder of work in order to get FreeSlash
and Freeslashcode hosted on

I was told that all files are to be tagged with copyright and license

Does that include build system files such as's? I have some text
data files for the program, and they are VERY sensitive to modification and
some of these template files cannot withstand comments, such as the Template
Toolkit files.

Normally, Template Toolkit templates are commentable, but the code that
sub-classed, and the data file it uses to provide items are not
commentable. And there are cases where the data will be output to the client's
browser and corrupt webpage.

How do I tag these troublesome project files with copyright and licensing
information? Can I just put a README file in the directory and add information
therein about COPY and LICENSE? Can I skip adding `copy and license' info on
files like AUTHORS, Changelog, or included example files (i.e,
'snippet-httpd.conf' or 'foo-data.txt') etc.?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]