GNU Savannah Evaluation for dri

Generated on Thu Jun 4 02:20:46 2015
Source: /tmp/gnu_eval.YM7nN7/./initramfs
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

A recognizable copyright statement was not detected in the following files.
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)

Projects hosted on GNU Savannah must carry a copyright statement.

For more information, see How to Apply GPL License to your source code.

NOTE:
If these files contain a legally acceptable copyright 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 statement will speed-up project approval on GNU Savannah.

hooks/peppe.sh

Files without canonical license statement

The following files contains statement that is possibly a valid license, but is not the caninocal statement text. For example:
This file is part of PACKAGE and is under the same license as PACKAGE
While this is legally a valid statement, it is better to include one of the canonical full license statements.

Another common reason for mis-detection is putting the license statement at the bottom of the file (it is recommended to put the license statement at the top of the source code file, right after the copyright statement).

Projects hosted on GNU Savannah must carry a license statement.

Please consider revising the license statement, to make it easy for future users and contributers of your project.

  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.

NOTE:
If these files contain any legally acceptable 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.
Using a standard license statement will speed-up project approval on GNU Savannah.

hooks/peppe.sh: # This file is in the public domain
initramfs.conf: # This file is in the public domain

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.

initramfs.conf

Possible misue of Linux vs GNU/Linux

The following files use the term Linux.

Linux is a Kernel, not a whole operating system. Please consider using the correct term GNU/Linux if the context is operating system and not Kernel-specific topic.

For more information, see Why GNU/Linux, Linux and GNU, and Words to Avoid.

hooks/peppe.sh: util-linux
hooks/peppe.sh:     /lib/*-linux-gnu/libnsl*.so \
hooks/peppe.sh:     /lib/*-linux-gnu/libnss_[cdf]*.so \

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
skipped (too-short) 2
no license detected 2

Summary of Analyzed Files

File Type no. lines Detected License Detected Copyright
modules text/plain 2 skipped (too-short) skipped (too-short)
initramfs.conf text/plain 10 (no copyright, perhaps too-small?)
hooks/peppe.sh text/x-shellscript 119
scripts/dummy.sh text/x-shellscript 7 skipped (too-short) skipped (too-short)

END OF EVALUATION REPORT