GNU Savannah Evaluation for alti

Generated on Tue Aug 11 03:22:05 2015
Source: /tmp/gnu_eval.IdmEKe/./alti
Detection script version: 0.1.1

NOTE:
This auto-generated report is in alpha-stage, and may contain incorrectly detected items.
Information here should be considered as informal suggestions and guidelines.
The official GNU Savannah Hosting Requirements can be found here: https://savannah.gnu.org/register/requirements.php

The following files are missing both copyright and license statement.

A copyright statement should be of form:
Copyright YEARS NAME
An optional "(C)" and/or contact addresses can be added if you wish, such as:
Copyright (C) YEARS NAME (email)

  1. If these are source code files for your project, consider using the standard license text at the beginning of your file. For GNU licenses, See How to GNU licenses for your own software
  2. If these are supporting/auxiliary files (such as Makefile, ini files), consider adding the GNU All Permissive License.

Projects hosted on GNU Savannah must carry a copyright and license statements.

NOTE:
If these files contain a legally acceptable copyright/license statement, they are acceptable for hosting on GNU Savannah (even if this auto-generated report failed to detect it).
Revising is not a strict requirement, but is highly recommended.
A recognizable copyright and license statements will speed-up project approval on GNU Savannah.

data/France_1000_XYZ_L93/MNT1000_L93_FRANCE.XYZ
data/France_1000_XYZ_L93/MNT1000_L93_FRANCE_XYZ.TXT

Small Source Code files without Copyright/License

The following small files were missing a copyright or license statement. Because these files are small (25 lines or less), it is possible that such a statement is not required, or a mention in the README file is sufficient.

Please review the list.
If these are source code files, please add a valid license and copyright statement.
If these are auxiliary files (such as Makefiles), consider adding the short GNU All Permissive License.

makefile

Problematic New-Line characters

The following file names contains potentially problematic new-line characters/ (such as CR+LF or just CR). Such files tend to cause problems on many computer systems, and are best avoided. Standard Unix files should use LF (\n) as a new-line character.

NOTE:
Revising these files is not a strict requirement, but is highly recommended.

data/France_1000_XYZ_L93/MNT1000_L93_FRANCE.XYZ
data/France_1000_XYZ_L93/MNT1000_L93_FRANCE_XYZ.TXT

Binary Data Files

The following files are binary data files (not textual source code files).

Some binary formats allow adding copyright and license information inside the file. For others, it is recommended to specify the copyright and license information in the README file.

  1. If you authored these files, please add copyright and license information in each file, or mention them in the README file.
  2. If you obtained these files from another source, you must verify and state their copyright and license information.
  3. Often times files that are free to download (as in 'no cost') are not Free to use (as in respect your freedom to usage, modify and distribute the files). Project hosted on GNU Savannah must not include non-free files.

NOTE:
This auto-generated report cannot detect if the README already mention these files.
If all data files in your project are properly copyrighted and licenses, please disregard this item.

Projects hosted on GNU Savannah must have a valid copyright and statement information for all data files.

alti.c
data/France_1000_XYZ_L93/MNT_L93_FRANCE.doc
data/Open_Licence.pdf
map_1000.bmp

Missing plain-text license file

Please include a plain-text license file, named either COPYING (for GPL-license) or LICENSE (for other licenses, such as BSD/MIT).

These are the commonly used file names, and using them will help future users and contributors for your project. If your project uses a non-standard name (e.g. license.gpl3 or bsd.txt, please consider renaming these files).

NOTE:
This is not a strict requirement, but is highly recommended.
Using a standard file name will speed-up project approval on GNU Savannah.

Missing plain-text README file

Please include a plain-text README file (or README.TXT, README.md, README.rst).

These are the commonly used file names, and using the will help future users and contributors for your project. If your project uses a non-standard name (e.g. info.txt or read-me-now, please consider renaming these files).

NOTE:
This is not a strict requirement, but highly recommended.
Using a standard file name will speed-up project approval on GNU Savannah.

Summary of Licenses

License Type no. files
GPLv3-or-later 8
skipped (non-code) 1
skipped (not-text) 4
skipped (too-short) 2
no license detected 3

Summary of Analyzed Files

File Type no. lines Detected License Detected Copyright
copying text/x-pascal skipped (non-code) skipped (non-code)
alti.c application/x-gzip skipped (not-text) skipped (not-text)
tools.h text/x-c 76 GPLv3-or-later 2015 slughnaz
makefile text/plain 20 (no copyright, perhaps too-small?)
bmp.c text/x-c 233 GPLv3-or-later 2015 slughnaz
tools.c text/x-c 136 GPLv3-or-later 2015 slughnaz
map_1000.bmp image/x-ms-bmp skipped (not-text) skipped (not-text)
xyz.c text/x-c 233 GPLv3-or-later 2015 slughnaz
map.c text/x-c 357 GPLv3-or-later 2015 slughnaz
data/licence text/plain 4 skipped (too-short) skipped (too-short)
data/France_1000_XYZ_L93/MNT_L93_FRANCE.doc application/msword skipped (not-text) skipped (not-text)
data/France_1000_XYZ_L93/MNT1000_L93_FRANCE.XYZ text/plain 571485
data/France_1000_XYZ_L93/MNT1000_L93_FRANCE_XYZ.TXT text/plain 50
data/Open_Licence.pdf application/pdf skipped (not-text) skipped (not-text)
map.h text/x-c 66 GPLv3-or-later 2015 slughnaz
arguments.txt text/plain 2 skipped (too-short) skipped (too-short)
xyz.h text/x-c 35 GPLv3-or-later 2015 slughnaz
bmp.h text/x-c 36 GPLv3-or-later 2015 slughnaz

END OF EVALUATION REPORT