taskSavannah Administration - Tasks: task #5230, Submission of Shrimpy

 
 

task #5230: Submission of Shrimpy

Submitter:  Dustin T. Harr <dharr>
Submitted:  Mon 06 Feb 2006 02:54:05 AM UTC
   
 
Should Start On:  Mon 06 Feb 2006 12:00:00 AM UTC Should be Finished on:  Thu 16 Feb 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 31 Jul 2006 06:33:35 PM UTC, comment #26: 

Hi,

If you would still like to have your project hosted at Savannah, please register it again.

The re-registration URL found in our acknowledgment of your earlier registration will direct
you to the proper location where you can re-register your project.

Regards.

Sebastian Wieseler <kickino>
Tue 25 Jul 2006 01:29:50 PM UTC, comment #25: 

Sorry, I don't have the time to deal with this any more for a while. I guess I will resubmit once I do.

Anonymous
Sat 01 Jul 2006 11:23:28 AM UTC, comment #24: 

Hi,

I am waiting for an answer from you.

If within one week I still do not get a reply, I will remove your project.
You will still be able to register it again once you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah?
If not, please tell us - we don't bite, and it will make us gain time.

Regards.

Sebastian Wieseler <kickino>
Fri 16 Jun 2006 08:24:47 PM UTC, comment #23: 

Hello.

At first, please remove GIF image files from your project and replace them with an other format (such as PNG or JPEG).

Because of the patents (Unisys and IBM) covering the LZW compression algorithm which are used when making GIF files,
it's impossible to have free software to generate proper GIFs.  These patents also apply to the compress program.

For more information, see http://www.gnu.org/philosophy/gif.html.

You should also add a README file in the directory of your image files and add there copyright+license notices for these files.
See also http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html


At second, 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.

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.

You can find some background and a possible migration script at https://savannah.gnu.org/forum/forum.php?forum_id=3766



And at last, some of your doc files (.html .py .txt) also lack information about copyright+license. You should add these notices to /every/ file of your documentation.


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


Regards,

Sebastian Wieseler <kickino>
Wed 14 Jun 2006 12:58:13 PM UTC, comment #22: 

Latest update.
http://zenerbufen.googlepages.com/

I have decided not to release the documentation under the FDL.

Dustin T. Harr <dharr>
Tue 13 Jun 2006 10:39:37 AM UTC, comment #21: 

Hi,

Can you let us know of any progress?

Regards

Steven Robson <stevenr>
Thu 18 May 2006 04:38:55 PM UTC, comment #20: 

Okay, feel like you get postponed, but please don't wait too long...

Sebastian Wieseler <kickino>
Thu 18 May 2006 01:37:07 PM UTC, comment #19: 

I have been very busy with midterms. I should have this in a day or two.

Dustin T. Harr <dharr>
Wed 17 May 2006 08:31:18 PM UTC, comment #18: 

Hi,

I am waiting for an answer from you.

If within one week I still do not get a reply, I will remove your project.
You will still be able to register it again once you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah?
If not, please tell us - we don't bite, and it will make us gain time.

Regards.

Sebastian Wieseler <kickino>
Thu 04 May 2006 09:51:05 PM UTC, comment #17: 

Hello. We look forward to your updated tarball.

Sebastian Wieseler <kickino>
Thu 04 May 2006 02:28:36 AM UTC, comment #16: 

Sorry for the long delay, My computer crashed and died horribly, My replacment just arrived. I should respond shortly.

Dustin T. Harr <dharr>
Wed 03 May 2006 09:05:37 PM UTC, comment #15: 

Hi,

I am waiting for an answer from you.

If within one week I still do not get a reply, I will remove your project.
You will still be able to register it again once you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah?
If not, please tell us - we don't bite, and it will make us gain time.

Regards.

Sebastian Wieseler <kickino>
Tue 25 Apr 2006 11:17:57 AM UTC, comment #14: 

Hello and sorry for the long delay. :-/

At first, please update your COPYING/LICENSE file with the new address of the FSF - http://www.gnu.org/licenses/gpl.txt


At second, your documentation lacks information about license and copyright. If you want to release it under the GNU FDL please read the instructions below:

In order to release your project 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.



Regards,

Sebastian Wieseler <kickino>
Mon 17 Apr 2006 10:55:24 AM UTC, comment #13: 
Dustin T. Harr <dharr>
Tue 04 Apr 2006 04:53:55 PM UTC, comment #12: 

Ok I gave this another shot. I think I got it this time.

Dustin T. Harr <dharr>
Tue 28 Mar 2006 09:58:16 PM UTC, comment #11: 

Hello.

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.

A statement like "File XYZ was released under GPL" is NOT enough.


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.

Regards and look forward to your updated tarball.

Sebastian Wieseler <kickino>
Sun 26 Mar 2006 12:02:26 AM UTC, comment #10: 

Latest release here: http://www.geocities.com/dr_zango

Dustin T. Harr <dharr>
Wed 15 Mar 2006 06:03:30 AM UTC, comment #9: 

Hello, and sorry for the very long delay. Can you please point me to the current tarball (which was released under the GPL)?

Regards,

Sebastian Wieseler <kickino>
Tue 28 Feb 2006 06:06:40 PM UTC, comment #8: 

Me and all the other devolopers currently working on this project would like all future versions to be released under GPL. We would of course keep an old copy availible on the site under the original license.

Would this be ok? If not I guess we can just keep it under the python license, I will go through and update the files with the new license information as soon as I hear back from you.

Dustin T. Harr <dharr>
Sat 25 Feb 2006 08:39:33 PM UTC, comment #7: 

Me and all the other devolopers currently working on this project would like all future versions to be released under GPL. We would of course keep an old copy availible on the site under the original license.

Anonymous
Sat 25 Feb 2006 08:05:28 PM UTC, comment #6: 

Hello.

Do you really need to change the licenses of these files?
We accept this license as it as, it is GPL compatible.

But please name the license explicitly in the files instead of the "(c) 1999 - AccesSoft - **See license.txt for details****"-line.

And (C) AccesSoft 1999 is a valid statement nevertheless. ;-)

Regards and hope that helps.

Sebastian Wieseler <kickino>
Fri 24 Feb 2006 05:27:50 PM UTC, comment #5: 

AccesSoft as far as I can tell does not exist any more. The website was removed and the original author left no other contact information.

here is the original AccesSoft license, Wouldn't it allow releasing a modified version under the GPL as long as a copy of the original license was included? saying something like previuse versions where availible with this license:

The license for the AccesSoft Version (identified as 1.1) is a follows:
Copyright 1999 by AccesSoft, Cupertino, California, USA.
Id: license.txt,v 1.2 1999/10/09 20:34:49 claudius Exp

All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright
notice and this permission notice appear in supporting documentation, and that
the name of AccesSoft not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.

The latest version of this code is made available by the AccesSoft at the
Internet address http://www.accessoft.com/moop .

ACCESSOFT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL ACCESSOFT
BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE

Dustin T. Harr <dharr>
Sun 19 Feb 2006 07:52:40 PM UTC, 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,

Sebastian Wieseler <kickino>
Thu 16 Feb 2006 04:43:25 AM UTC, comment #3: 

Is it possible to change the project name?

Full Name:
----------
PyMoo

System Group Name:
-----------------
pymoo

Dustin T. Harr <dharr>
Tue 14 Feb 2006 01:29:22 AM UTC, comment #2: 

1:

python: http://www.python.org/2.4.2/license
pygame: GNU LGPL version 2.1
pyopengl: http://pyraf.stsci.edu/LICENSES/license.txt
numeric(numpy): GPL
MOOP: http://cvs.sourceforge.net/viewcvs.py/moop/moop/LICENSE?view=markup

Joshua Macy has passed on 'MOOP' to me, dustin harr. previously  Joe Strout passed on MOOP to Joshua Macy

2: I thought I had submitted to savannah.nongnu.org my apologies if I sent it to the wrong site.

MOOP is currently on sourceforge but will be removed as soon as MOOP is moved to savannah.nongnu.org MEEP will be added and the  combination of the two I would like to host on savannah.nongnu.org

Dustin T. Harr <dharr>
Mon 13 Feb 2006 05:16:50 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.


At first, can you please point me to the websites of the software you require? Or to their license pages (best solution). :-)



At second, Savannah is a central point for development, distribution and maintenance of GNU Software.

There is a companion site savannah.nongnu.org where we also host Free Software projects that are not part of the GNU Project, but run on free platforms.

However, we do not allow to host your project on Savannah and
SourceForge at the same time, if Savannah is just a project mirror.
Your project development should happen primary on Savannah.

How do you plan to use your Savannah account?



At third, I don't have a look at your source code because of (2.).


If you are willing to answer all questions above, 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.

Sebastian Wieseler <kickino>
Mon 06 Feb 2006 02:54:05 AM UTC, original submission:  

A new project has been registered at Savannah
The project account will remain inactive until a site admin approve or discard the registration.


######### REGISTRATION ADMINISTRATION #########

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific "Group Administration" page, accessible only to site administrators, effectively logged as site administrators (superuser):

  <https://savannah.nongnu.org/admin/groupedit.php?group_id=8334>


######### REGISTRATION DETAILS #########

Full Name:
----------
  Shrimpy

System Group Name:
-----------------
  shrimpy

Type:
-----
  non-GNU software & documentation

License:
--------
  GNU General Public License V2 or later

Description:
------------
  This is a (graphical) mud written in python and using python as the ingame programming language. The purpose is to demonstrate how to do things in python that are commonly claimed hard or impossible to do as well as provide a fun game like environment where people can learn to program online/in game.

I am the current maintained of the opensource project MOOP which will be used for the server side and the author of the client MEEP and want to bring both together under one project here and release all new versions under the GPL license.

http://moop.sourceforge.net/  < server
http://shro.objectis.net/meep_preview.zip/view < client

Other Software Required:
------------------------
  Dependancies include:
python
and for the client:
pygame
pyopengl
numeric




Dustin T. Harr <dharr>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 13 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-07-31 kickino StatusPing-ed Cancelled
    Open/ClosedOpen Closed
2006-07-01 kickino StatusIn Progress Ping-ed
2006-05-18 kickino StatusPing-ed In Progress
2006-05-17 kickino StatusWait reply Ping-ed
2006-05-04 kickino StatusPing-ed Wait reply
2006-05-03 kickino StatusWait reply Ping-ed
2006-03-28 kickino StatusIn Progress Wait reply
2006-03-15 kickino StatusWait reply In Progress
2006-02-19 kickino Percent Complete0% 40%
2006-02-19 kickino StatusNeed Info Wait reply
2006-02-13 kickino StatusNone Need Info
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-d3ae.
Corresponding source code