[Top][All Lists]

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

Re: [Savannah-hackers] submission of SwitchCfg v1.0 - savannah.nongnu.or

From: Jonathan Gonzalez V.
Subject: Re: [Savannah-hackers] submission of SwitchCfg v1.0 -
Date: Fri, 07 Jan 2005 13:46:28 -0300
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)

"Joe Knecht" <address@hidden> writes:

Hi Joachim,

I reviewed the source code that you send me. In the Copyright notices
you must use the '(C)' with an upper case C. In addition to this you
must use a list of years, if you put a '/' between years will drive
the user to a confusion if it is or not a range of years, preferably use
a , (coma) to separate the list of years.

You have the Copyright and License notices missing in some files,
consider to fix this. Remember that any file with more than ten lines
long should carry on a Copyright and License notices, this rules
include Makefiles(generated by hand), shell scripts, etc.

To avoid confusions about how to apply a proper Copyright and License
notices, consider to read these URLs:

If you are willing to make the changes mentioned above, please provide
us with an URL to an updated tarball of your project.  Upon review, we
will reconsider your project for inclusion in Savannah.


> Hi Jonathan,
> here it is.
> I've already read the GNU howto's and included GPL/FDL information.
> The project itself is stable (or so I believe) and tested. We will use it in
> our company's production environment starting mid of January.
> Best regards
> Joe Knecht
> ----- Original Message ----- 
> From: "Jonathan Gonzalez V." <address@hidden>
> To: <address@hidden>
> Cc: <address@hidden>
> Sent: Friday, January 07, 2005 3:54 PM
> Subject: Re: [Savannah-hackers] submission of SwitchCfg v1.0 - 
> Hi Joachim,
> I'm evaluating the project you submitted for approval in Savannah.
> Please, send the tarball to my email address (address@hidden).
> We wish to review your source code, even if it is not functional, to
> catch potential legal issues early.
> For example, to release your program properly under the GPL you must
> include a copyright notice and permission-to-copy statements at
> the beginning of every file of source code.  This is explained in
>  Our review would help catch
> potential omissions such as these.
> Regards,

"Emacs the only editor which has its own church"

Attachment: pgpmS6xn95ofj.pgp
Description: PGP signature

reply via email to

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