taskSavannah Administration - Tasks: task #8986, Submission of ClanBomber

 
 

task #8986: Submission of ClanBomber

Submitter:  Rene Lopez <rsl>
Submitted:  Tue 13 Jan 2009 04:18:50 PM UTC
   
 
Should Start On:  Tue 13 Jan 2009 12:00:00 AM UTC Should be Finished on:  Fri 23 Jan 2009 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  sgerhardt Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Thu 15 Jan 2009 05:01:32 PM UTC, comment #18: 

Then I think the best option is to delete the tar, after all if somebody downloads it she will not be able to compile it. I will be only a short time as I already removed clanstring.h as a dependency (the code now uses std::string).

Rene Lopez <rsl>
Thu 15 Jan 2009 04:49:59 PM UTC, comment #17: 

Oh, I didn't know about this NexT user link issue.
I assumed we were just to object if a Savannah project has some proprietary dependencies. But if NexT wasn't allowed to this, we shouldn't do it here either.

Rene, under these circumstances, I think it is better to delete the direct pointer in the ReadMe to the old Clanlib files. This way, nobody can assert that you were trying to push the users to do something that you yourself can't legally do.

Sebastian Gerhardt <sgerhardt>
Thu 15 Jan 2009 06:26:36 AM UTC, comment #16: 

I've started to substitute code using them but it make take a while; at least I expect to remove all clanstring.h dependencies this weekend.
I already posted the code that depends on those files, should I remove it?

Rene Lopez <rsl>
Thu 15 Jan 2009 12:42:59 AM UTC, comment #15: 


> The only other solution I can think of is to strip of all old
> clanlib files from the project and tell the users where to find
> them


I'm sorry, but "user does the link" was not a solution for NeXT in porting GCC, and it's not a solution here.  As long as the program needs the files, they are effectively part of the package, whether they are distributed separately or not.

In other words, the files must be relicensed (by their authors) or the need for them eliminated.

IMHO, we don't think we need to go so far as to undo your project registration, as long as you promise to make the rewrite to use the standard classes (or backporting other compatible code) a priority.  Ok?

Thanks,
Karl

Karl Berry <karl>
Site Administrator
Wed 14 Jan 2009 12:44:25 PM UTC, comment #14: 

Thanks, I hope to make a release with no clanlib requirements this weekend.

Rene Lopez <rsl>
Wed 14 Jan 2009 12:37:38 PM UTC, comment #13: 

Ok, please do so.

I did not find any other issues. Therefore I can approve this now.
Welcome aboard. :)

The daemons will create the hosting environment in the course of the next hours.

Good luck with your project.

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 12:21:43 PM UTC, comment #12: 

Then I will take them out and point the users to where they can be find, rewrite or backport them is not a good idea. The best thing is to replace them with c++ standard classes that come with the compiler as they have a very similar style and methods, but it will take me some time to do.

Rene Lopez <rsl>
Wed 14 Jan 2009 12:11:02 PM UTC, comment #11: 

I see.
The problem is, you can't legally distribute the package under GPLv2+ with these GPLv2only files.
But "or any later" is required by Savannahs policy.

The only other solution I can think of is to strip of all old clanlib files from the project and tell the users where to find them, until they have either been rewritten, replaced or the original authors gave their permission to relicense.
Maybe you can "backport" the current BSD clanlib files?

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 11:55:52 AM UTC, comment #10: 

The only file still present in Clanblib 0.8.x series is clanstring.h which fails to compile with the game. The other 3 files are only present until 0.2.x and have the same header (no copyright notice).
vector.h is the only one having something that resembles a copyright notice:
  1999/06/19 Daniel Vogel

totally replaced old CL_Vector with this code

Rene Lopez <rsl>
Wed 14 Jan 2009 11:14:15 AM UTC, comment #9: 

I have planned to substitute them with std::string std::vector std::list. CLString is partially removed from the game but I will try to compile with the current clanlib versions to see if the game compiles.

Rene Lopez <rsl>
Wed 14 Jan 2009 11:04:35 AM UTC, comment #8: 

Ok, the art section looks very good now.

I think there are 4 problematic source files left:
clanstring.h array.h cl_vector.h link.h

They do not include a copyright line and they seem to be licensed under GPL version 2 only. Do you know a solution for this?
I know Clanlib has been released under BSD for some years know, maybe you could replace it with a new version, because BSD 3 clause  license is compatible with GPLv2+.

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 10:45:09 AM UTC, comment #7: 

Oh, nice. 2 seconds short :)

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 10:44:44 AM UTC, comment #6: 

Please upload the new tarball then with the form below.

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 10:43:42 AM UTC, comment #5: 
Rene Lopez <rsl>
Wed 14 Jan 2009 10:16:32 AM UTC, comment #4: 

Well I sent you a mail because savannah kept rejecting my coments here but now it is working, stange.
As I said in my previous comment the debian dir is deleted and the problem with the README files is because I made a make dist after uploading, and the new file have them.

Rene Lopez <rsl>
Wed 14 Jan 2009 10:05:08 AM UTC, comment #3: 

Hi.
So the README files in each directory are not enough (they have the
license info at the end), or is because I need to put each one of them on separete files.
I already deleted the debian directory.

Rene Lopez <rsl>
Wed 14 Jan 2009 09:57:03 AM UTC, comment #2: 

Rene wrote:

>I'm sorry if you don't want mail delivered directly to you


I get the mail sent by Savannah anyway if anything is written in the comment field of the tracker.
But it is preferred to write directly in the task tracker because it helps me to keep the discussions in different task apart from each other. :)


>So the README files in each directory are not enough (they have
>the license info at the end), or is because I make it ambiguous or
>something.


In the package you have uploaded, there is no such readme in the src/pics directory for example.

#Even image files and sound files should contain copyright
#notices and license notices, if they can. Some formats do not
#have room for textual annotations; for these files, state the
#copyright and copying permissions in a README file in the same
#directory.
http://www.gnu.org/prep/maintain/maintain.html#Copying-from-Other-Packages

The reasoning behind this is that there are many game projects whose source is under a free license, but this doesn't apply for the art, especially in regard to commercial use and modification.
I assume all art of this package was meant to be licensed freely, because otherwise it would not have been accepted by Debian main in the first place. But we prefer to have an explicit statement about this, so that it never will be misunderstood.

So for example in the pics directory, there could be a README saying something like "All graphic files in this directory are are part of ClanBomber and licensed under GPLv2 or any later". (If this was the original author's intent, that is)

If you don't want to put it into every directory, at least the Readme in the main directory should make a statement about this.
"Clanbomber \n Copyright xyz \n All source, graphics, ... of this package are licensed under xy, except the fonts which are under zx..."

Sebastian Gerhardt <sgerhardt>
Wed 14 Jan 2009 08:55:54 AM UTC, comment #1: 

Hi there.

Do you think you can strip of the debian directory first?
This would make the review a little easier, because the license version is a bit ambivalent there and we had to query the original authors otherwise, which may take some time.

Also, we need to be sure about the license the "game content" is under (maps, sound&gfx). A proper license note should be in each of these directories, stating all the content is licensed under this or that license. Alternatively, this copyright note could be embedded directly in the comment header of the pngs and waves.

The source code itself seems all fine. If you attach an upgraded tarball with the above changes, I think the project is ready for approval.

Sebastian Gerhardt <sgerhardt>
Tue 13 Jan 2009 04:18:50 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards 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):



Registration Details


  • Name: ClanBomber
  • System Name:  clanbomber
  • Type: non-GNU software & documentation
  • License: GNU General Public License v2 or later (Bitstream Vera license for fonts.)





Description:

ClanBomber is a game that is similar to Bomberman its written in c++. I'm trying to keep it alive because its original developers are not active and the original code is only works in directf, which is linux specific.
My current code now can be run from X11 and should be able to run in any posix system.
It uses autotools for compilation, so it must be relative easy to install.
Is was special enough to be included in debian, but they have droped it because of dependace of old libraries (for version 1) and dependace of directfb (for version 2).


Other Software Required:

SDL LGPLv2.1 http://www.libsdl.org/
SDL_image LGPLv2.1 http://www.libsdl.org/projects/SDL_image/
SDL_mixer LGPLv2.1 http://www.libsdl.org/projects/SDL_mixer/
SDL_ttf LGPLv2.1 http://www.libsdl.org/projects/SDL_ttf/
SDL_gfx LGPLv2.1 http://www.ferzkopp.net/joomla/content/view/19/14/
Boost Boost license http://www.boost.org/


Other Comments:

I find amusing that this little the only reason 4 of my little cousins use my GNU/Linux sistem when they come home; they like it, even when they have Nintendo DS's.


Tarball URL:

http://savannah.gnu.org/submissions_uploads/clanbomber2-2.1.0.tar.gz


Rene Lopez <rsl>

 

(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

 

Carbon-Copy List
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by rsl (Submitted the item)
  •  

    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 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-01-14 sgerhardt StatusIn Progress Done
        Percent Complete70% 100%
        Open/ClosedOpen Closed
    2009-01-14 sgerhardt StatusNone In Progress
        Percent Complete0% 70%
        Assigned toNone sgerhardt

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code