taskSavannah Administration - Tasks: task #8806, Submission of PHP Binding for SDL

 
 

task #8806: Submission of PHP Binding for SDL

Submitted by:  Dimitri Giardina <sidd6892>
Submitted on:  Mon 27 Oct 2008 10:14:09 PM UTC  
 
Should Start On:  Mon 27 Oct 2008 12:00:00 AM UTC Should be Finished on:  Thu 06 Nov 2008 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  -Deleted Account- <nicalvaro>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Mon 15 Dec 2008 07:06:55 PM UTC, comment #15:

Hi,

I have approved your project as non-GNU. You will receive an automated e-mail containing detailed information about the approval.

I noted you request an "Official GNU software" project. If you would like to offer your project to the GNU project, please contact the GNU Eval team, following the instructions at http://www.gnu.org/help/evaluation.html .

Welcome at Savannah!

Sylvain Beucler <Beuc>
Thu 11 Dec 2008 11:22:34 PM UTC, comment #14:

ok.
i resend files with your changes.
included README (with instructions)
removed sdl.so binary.
(probably there's something to change into the definition of the extension. name into license will be phpsdl-ng).

waiting your response,
best regards.

(file #17031)

Dimitri Giardina <sidd6892>
Thu 11 Dec 2008 10:35:12 PM UTC, comment #13:

ok. what should i do?
provide a patch file for my sent code? (in order to vary the GPL text inside?)

waiting. bye

Dimitri Giardina <sidd6892>
Thu 11 Dec 2008 10:00:12 PM UTC, comment #12:

> if you say this: http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#TOCIfInterpreterIsGPL, it only tell me that if i write a perl or java or python extension with GPL or other licenses, i have to respect that licenses.


This FAQ says that you can write programs in perl/java/php/python independently of the interpreter license. phpsdl-ng, however, is a core extension and is not written in PHP, but designed to work as a C module for PHP.
Check for "bindings" at http://www.gnu.org/licenses/gpl-faq.html#InterpreterIncompat

Note: as you wrote all the GPL'd code, you could write an exception as explained at:
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs

(Thanks for the other examples of GPL'd PHP extensions :))

Sylvain Beucler <Beuc>
Thu 11 Dec 2008 08:46:53 PM UTC, comment #11:

... i don't want to publish the binary.
if i want to publish bin code, not in this site ;) (if there are any **valid** problems about it)

generated sdl.c (if you want i send you the generated code) **use** php api, and **use** sdl api, and use **libc** api...

if you say this: http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#TOCIfInterpreterIsGPL, it only tell me that if i write a perl or java or python extension with GPL or other licenses, i have to respect that licenses.

i generate only GPL-2.0 code.

ehm: some GPL-2.0 extensions of php
http://sourceforge.net/projects/turck-mmcache
http://eaccelerator.net/

... so using PHP API into a GPL code is not a problem.

SDL: LGPL.
there's some other problem?

waiting your response.

Dimitri Giardina <sidd6892>
Thu 11 Dec 2008 06:52:07 PM UTC, comment #10:

Hi,

I'd love to see phpsdl-ng use the GPL, but I'm not sure it's possible here.

phpsdl-ng will link with PHP to produce a core module in shared-object (.so) form, so I believe phpsdl-ng needs to be compatible with the PHP license.

As we mentioned, the PHP license isn't compatible with the GNU GPL, however the GNU LGPL is compatible.

I know of a GPL'd PHP module though (http://lasso.entrouvert.org/) - Karl, what do you think?

Sylvain Beucler <Beuc>
Tue 09 Dec 2008 09:52:03 AM UTC, comment #9:

you can ignore the binary included and send an email to administrators with this comment. i'll remove it when the project is approved.
the license is GPL-2.0.
the c-code of the extension will be generated into that license.

bye
Dimitri

Dimitri Giardina <sidd6892>
Sun 07 Dec 2008 07:09:30 PM UTC, comment #8:

Well, alright. I am little confused, but if you believe that is the way it should be, then okay. The Administrators will have to approve your project though.

-Deleted Account- <nicalvaro>In charge of this item.
Wed 03 Dec 2008 01:10:56 PM UTC, comment #7:

> I am not sure why there is a binary in
> the tarball. It is called sdl.so

You can ignore that sdl.so (binary).

> A few of the files I guess could still use a
> license notice. They are sdl_stuff.c and bu2.

sdl_stuff.c is used to generate sdl.c when you generate code with gen_ext.php. you can ignore bu2 (a script file)
the generated sdl.c will contain GPL-2 license code.

waiting your response.

Dimitri Giardina <sidd6892>
Wed 03 Dec 2008 12:05:48 AM UTC, comment #6:

I am not sure why there is a binary in the tarball. It is called sdl.so

A few of the files I guess could still use a license notice. They are sdl_stuff.c and bu2.

-Deleted Account- <nicalvaro>In charge of this item.
Mon 01 Dec 2008 12:15:53 PM UTC, comment #5:

hi.

1) i've inserted gpl-2.0.txt into the package.
2) i've inserted gpl-2.0 license into gen_fun.php; note that that file in the future will be included in a standalone package
3) sdl_stuff.c and sdl_globals.c are stuff, that with the gen_fun.php script will be used to generate sdl.c, the code for extension itself; when sdl.c will be generated, it will include gpl-2 code (present into the sdl.xml xml definition).

if you have some problems to understand me, please send me a email.

best regards

(file #16959)

Dimitri Giardina <sidd6892>
Sun 30 Nov 2008 01:11:14 AM UTC, comment #4:

> 3. http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Code.html#License-Notices-for-Code


Whoops! I made an error on the last comment. Instead of using that link, please use this guide [1] for help on making a license notices for all your files. Be sure to use the license notice made for multiple files rather than the one file program license notice.

1. http://www.gnu.org/licenses/gpl-howto.html

-Deleted Account- <nicalvaro>In charge of this item.
Sun 30 Nov 2008 12:54:15 AM UTC, comment #3:

> i'm rewriting the extension from zero.

That's great! I got a little confused with the description of rewriting another project. The php-sdl project has no code. I had mistaken that project for another. Please provide additional information about what your project is for and what you hope to accomplish with it.

> i've also to use some license.
> 1) first of all, if i use only the api (the calls) to a LGPL library, i've to use LGPL also for my project (for SDL that is LGPL)


I believe it is legal to copy and to use API calls to this program from a GPL licensed program as those licenses are compatible with each other.

> 2) idem for php (PHP License).


Provide a link to this project. Is this a dependency or are you copying from this project? The PHP license is incompatible to the GPL, according to gnu.org [0], so you should not copy between the projects.

0. http://www.gnu.org/licenses/license-list.html

> 3) i want to maintain all my code into GPL(2).


The tarball must contain a copy of the GPL license. You say you want to use GPL(2). The old version of this license can be found here [1]. You may want to consider using the GPL v3 [2].

1. http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
2. http://www.gnu.org/licenses/gpl.txt

Place your copyright and license notice in all non-trivial files and files longer than 10 lines. You may want to consult the guide for License notices [3]. Be aware that this guide explains using a license notice for the GPL v3 and not GPL v2. Switch the 3 for a 2.

3. http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Code.html#License-Notices-for-Code

My apologies for any confusion I may have caused and thank you for considering Savannah.

-Deleted Account- <nicalvaro>In charge of this item.
Sat 29 Nov 2008 04:14:03 PM UTC, comment #2:

i'm rewriting the extension from zero.
i've also to use some license.
1) first of all, if i use only the api (the calls) to a LGPL library, i've to use LGPL also for my project (for SDL that is LGPL)
2) idem for php (PHP License).
3) i want to maintain all my code into GPL(2).

it's possible?

i'm sending you a starting point for my extension.

note that some code is php, some code is "meta-code" in xml, some other code is m4 macros, and some other code is c.

probably i'll use php code for making a fast mode to write php extensions.

waiting your response,
best regards.

Dimitri Giardina

(file #16942)

Dimitri Giardina <sidd6892>
Mon 17 Nov 2008 01:39:31 AM UTC, comment #1:

I am not sure I understand. Your application claims this is Official GNU Software, it needs more info, and the link does not contain a tarball.

The licensing FAQ explains that using the GPL does not make it official GNU software [1].

I took a quick look at the PHP-SDL source and it has a few files that contain copyright notices for the PHP 2.02 license. The project page [2] claims that it released under the LGPL, but there is neither a license file for the PHP license nor the LGPL. According the the Savannah wiki, if you are to copy any code from that project, you'll have to ask the authors. [3]

[1] http://www.fsf.org/licensing/licenses/gpl-faq.html#DoesUsingTheGPLForAProgramMakeItGNUSoftware

[2] http://sourceforge.net/projects/phpsdl/

[3] http://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly

-Deleted Account- <nicalvaro>In charge of this item.
Mon 27 Oct 2008 10:14:09 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: PHP Binding for SDL
  • System Name:  phpsdl-ng
  • Type: Official GNU software
  • License: GNU General Public License v2 or later

Description:

Rewriting of php-sdl; a try to know how to write php extensions.

Tarball URL:

http://www.google.it

Dimitri Giardina <sidd6892>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #17031:  phpsdl-0.0.1.tar.gz added by sidd6892 (25KiB - application/x-gzip)
file #16959:  phpsdl_work.tgz added by sidd6892 (57KiB - application/x-tar)
file #16942:  phpsdl.tgz added by sidd6892 (10KiB - application/x-compressed-tar - source file.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by nicalvaro (Posted a comment)
  • -email is unavailable- added by sidd6892 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-12-15 Beuc StatusNeed Admin => Done
        Open/ClosedOpen => Closed
    2008-12-11 sidd6892 Attached File- => Added phpsdl-0.0.1.tar.gz, #17031
    2008-12-07 nicalvaro StatusNone => Need Admin
        Assigned toNone => nicalvaro
    2008-12-01 sidd6892 Attached File- => Added phpsdl_work.tgz, #16959
    2008-11-29 sidd6892 Attached File- => Added phpsdl.tgz, #16942

    Back to the top


    Powered by Savane 3.4