savannah-register-public
[Top][All Lists]
Advanced

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

[Savannah-register-public] [task #4072] Submission of otl


From: Sylvain Beucler
Subject: [Savannah-register-public] [task #4072] Submission of otl
Date: Fri, 27 May 2005 20:28:31 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.6) Gecko/20050512 Firefox/1.0 (Ubuntu package 1.0.2)

Update of task #4072 (project administration):

                  Status:                 Ping-ed => Wait reply             

    _______________________________________________________

Follow-up Comment #6:

Hello,

To move your project to Savannah, you need to tell SourceForge about it.

This page
https://sourceforge.net/project/admin/removal.php?group_id=132991
should point you to a form where you can mention a project "relocation".

Since your project do not use the SourceForge CVS repository, you will only
need to upload your tarballs to the Savannah download area once the project
is approved (check the Savannah FAQ for details).


Your project complies with Savannah's requirements and can be hosted here.

Before to host your files however, we ask that all files carry an appropriate
copyright and license notice.


Here is the standard instructions we have:
In order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the
beginning of every file of source code.

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
information.

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,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.


In your case, you need to add notices to the tag-remove.pl files, as well as
a README file for your gui/* data.


Also, the address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Updates versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.

If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project.

Regards.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=4072>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/





reply via email to

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