[Savannah-register-public] [task #5230] Submission of Shrimpy

[Sebastian Wieseler]

Update of task #5230 (project administration):

                  Status:               Need Info => Wait reply             
        Percent Complete:                      0% => 40%                    

    _______________________________________________________

Follow-up Comment #4:

Hello.

Okay, let's begin (I changed your system name the other things can you change
after the registration).


At first, if you are the only copyright holder you can change the license
(python->GPL) on your own, if not, please ask the copyright holder(s) if
he/she(/they) accept(s) the license change or distribute some files under the
python license.



About: "(c) 1999 - AccesSoft - See license.txt for details"
At second, if this file was released under the python-license include, it the
license in the file or at least name the license explicitly.

At third, is the copyright holder refered to in the copyright notices
(==AccesSoft), a legal entity that can be assigned copyright?
If not, you need to add the author(s)' name(s) instead.

Check http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
for more information, and update your files.



At fourth, to release your files (or the files of other if they accept the
license change, too) under the terms of the GPL:

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.

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.



At fifth, I  saw that your documentation lacks any information about
copyright and license please include there such information.

In order to release your project^documentation properly and unambiguously
under the FDL,
please place copyright notices and permission-to-copy statements after the
title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING'
(http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.



At sixth, "MOOP is open source" - note that Savannah supports projects of the
Free Software movement, not projects of the Open Source movement.

We are careful about ethical issues and insist on producing software that is
not dependent on proprietary software.

While Open Source as defined by its founders means something pretty close to
Free Software, it's frequently
misunderstood.
For more information, please see
http://www.gnu.org/philosophy/free-software-for-freedom.html.


Regards,

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/