[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #4672] Submission of demidemazeta
From: |
Davidlohr Bueso Arnett |
Subject: |
[Savannah-register-public] [task #4672] Submission of demidemazeta |
Date: |
Tue, 27 Sep 2005 17:12:39 -0400 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) |
Follow-up Comment #5, task #4672 (project administration):
Hi,
If you haven't read my last email, please, read the follow text:
The license does not contain the last section, titled "How to Apply These
Terms to Your New Programs".
Please use a complete verbatim copy of the license, which may be found at
http://www.gnu.org/licenses/gpl.txt, http://www.gnu.org/licenses/lgpl.txt or
http://www.gnu.org/licenses/fdl.txt.
The license must be copied verbatim and in its entirety.
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:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt
You can find some background and a possible migration script at
https://savannah.gnu.org/forum/forum.php?forum_id=3766
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 file of source code:
Makefile
src/cursor.cpp
src/parser/parser.lex
src/parser/parser.yacc
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, like the
bin directory), 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.
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
replies.
Regards.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?func=detailitem&item_id=4672>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Tobias Heinzen, 2005/09/18
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Davidlohr Bueso Arnett, 2005/09/19
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Davidlohr Bueso Arnett, 2005/09/23
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Tobias Heinzen, 2005/09/23
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Davidlohr Bueso Arnett, 2005/09/27
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Tobias Heinzen, 2005/09/27
- [Savannah-register-public] [task #4672] Submission of demidemazeta,
Davidlohr Bueso Arnett <=
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Tobias Heinzen, 2005/09/28
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Davidlohr Bueso Arnett, 2005/09/28
- [Savannah-register-public] [task #4672] Submission of demidemazeta, Tobias Heinzen, 2005/09/28