[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #6746] Submission of Jalali Calendar Li
[Savannah-register-public] [task #6746] Submission of Jalali Calendar Library
Sun, 22 Apr 2007 21:00:54 +0000
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20070310 Iceweasel/184.108.40.206 (Debian-220.127.116.11-2)
Update of task #6746 (project administration):
Status: None => Wait reply
Assigned to: None => sp
Follow-up Comment #1:
I'm evaluating the project you submitted for approval in Savannah. While
doing so I have noticed a few problems which are described below.
First of all, the address of the FSF has changed, and is now:
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Please update your license notices.
Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.
Updated versions of the GPL, LGPL and GFDL can also be found at:
You can find some background and a possible migration script at
Secondly, in order to release your project properly and unambiguously under
the GNU GPL, please place copyright notices and permission-to-copy statements
at the beginning of every copyrightable file, usually any file more than 10
In addition, if you haven't already, please include a copy of the plain text
version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into
a file named "COPYING".
For more information, see http://www.gnu.org/licenses/gpl-howto.html.
If some of your files cannot carry such notices (e.g. binary files), then you
can add a README file in the same directory containing the copyright and
license notices. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further
The GPL FAQ explains why these procedures must be followed. To learn why a
copy of the GPL must be included with every copy of the code, for example,
Also, please note that this is not the GNU Evaluation. This is the Savannah
evaluation, to check whether your project complies with the Savannah hosting
rules (a subset of the GNU Evaluation policies), and get a place to host your
If you do not want to host your project here, but want to have your project
evaluated by the GNU Eval team, then you only need to write to
Can you clarify this point?
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.
To help us better keep track of your registration, please use the tracker's
web interface following the link below. Do not reply directly, the
registration process is not driven by e-mail, and we will not receive such
Reply to this item at:
Message sent via/by Savannah