taskSavannah Administration - Tasks: task #10086, Submission of phpDebate

 
 

task #10086: Submission of phpDebate

Submitter:  Luka M. <paxcoder>
Submitted:  Mon 11 Jan 2010 03:21:07 PM UTC
   
 
Should Start On:  Mon 11 Jan 2010 12:00:00 AM UTC Should be Finished on:  Thu 21 Jan 2010 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  marioxcc Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sun 31 Jan 2010 02:52:23 PM UTC, comment #18: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 31th 2010 in GNU Savannah task 10086: "Submission of
phpDebate"

Ok, submission removed.

Item status changes:

Status -> Cancelled
Open/Cloesd -> Closed
Assigned to -> marioxcc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktlmRcACgkQZ4DA0TLic4iZkQCgh+TFhc9uFv4p27tKpLgjzYn7
KbUAnRNMk4gxJNJLhqGuwl2S3nvaJQK8
=gwXj
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sun 31 Jan 2010 12:11:42 PM UTC, comment #17: 

Yes, the "submission" is my project. You can remove it. I'll host it myself.

Luka M. <paxcoder>
Sat 30 Jan 2010 11:43:37 PM UTC, comment #16: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 30th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

Well, project hasn't been approved so it can't be deleted.

Are you requesting the deletion of the submission?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktkxA8ACgkQZ4DA0TLic4grUwCfRHUimmdouG+2I+j0O7gMlNbv
cCwAnAnDXMOrZvQlQWlTJsRrwAnTyARD
=hxUy
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sat 30 Jan 2010 06:13:50 PM UTC, comment #15: 

Feel free to remove the project.

Luka M. <paxcoder>
Sat 30 Jan 2010 05:36:06 PM UTC, comment #14: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 30th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

Copyleft is almost always good but isn't nessesary for small
things such as those files.

But as you want (Or wanted) to use the GNU GPL, I ask you to use the
full header, because that is the better way to use it.

I don't see the contradiction, if you want to copyleft do it in the
standard way, if not, then put it under public domain.  I always
encourage copyleft, but that is up to you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktkbfsACgkQZ4DA0TLic4gu3ACeM+mpOFra5Lb3kmMRjA8Q0zG0
XxsAniKoRQfrrtecmJ0WhHJE3g8HD7A8
=hk2l
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sat 30 Jan 2010 03:20:08 PM UTC, comment #13: 


>You could have one line saying something like "This file is public domain. Originally written 2010, Luka M."
>I agree with Karl, I suggest public domain if you want a tiny header for that files


You suggested I use the full notice so there won't be any confusion as to the protection of users rights. Now you suggest I give up those rights (we're talking about copyleft) just so that I can have a shorter notice. I find this... well I don't really have a word for it. Contradictory perhaps?

If I include short GPL notice, the worst case scenario is that it'll be treated as public domain by those who will disregard it or theoretically try to contest it. Plus I lose copyright.

Luka M. <paxcoder>
Sat 30 Jan 2010 02:18:44 AM UTC, comment #12: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 29th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

>I'm just trying to make it shorter.


>And if you look around savannah, there is a plethora of different
>notices of different sizes and contents. I am not doing anything
>wrong


We ask the mantainers of project that includes files with no/bad
copyrigth licence (Such as images and some auto generated files) to
clarify the licence in the README file.

About the wdiff issue, I will investigate later and ask the mantainer
to correct if nessesary but most likley is an autoheader issue.  When
you think you found a mistrake in savannah, we will thank you for
reporting it, but we won't make an exeption to you, but instead, we
will try to repair it, of course.  The mistrake of other persons are
not an excuse to you make the same mistrake, but an reminder to take
more care.

There is no justification to make the GPL header shorter, it is fine
as is, if you want to GPL-licence, do it in that way.

Of course, is not mandatory to use the GNU GPL, in overall we accept
any free GPL-compatible licence for code and FDL-copatible for
documentation, also we accept public domain (That is, no copyrigth at
all).

I agree with Karl, I suggest public domain if you want a tiny header
for that files, remember you MUST state the file is public domain like
the one Karl suggested.  No licencing information at all is
confussing, and may be taked as a fully propietary licence if someone
distributes that file only (With the rest of program striped).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktjlowACgkQZ4DA0TLic4i17wCfY9Ex+eVc01/xr0KU+26Jzf1r
88sAnR7avVdoyFFRfgIDsUSRDV2pu0vk
=dpnQ
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sat 30 Jan 2010 12:36:23 AM UTC, comment #11: 

No question that there are many pre-existing GNU packages (let alone non-GNU packages) which don't follow the recommendations.  As far as GNU goes, we try to get those fixed.  But those are bugs, not acceptable practices. We don't want to compound the problem.

Part of the goal for savannah, as rms has defined it, is to implement and require the best practices for licensing.  Thus, using recommended license notices.

I appreciate the cluttering effect of 12 more lines in lots of small source files.  If the source files are so small, perhaps the GPL does not really confer much benefit.  You could have one line saying something like "This file is public domain.  Originally written 2010, Luka M."



Karl Berry <karl>
Site Administrator
Fri 29 Jan 2010 11:29:34 PM UTC, comment #10: 

But would they require it and insist and disallow submission if I don't comply? I don't think so.
As far as I've seen, there are files on this site that don't even have a copyright notice - not even a single line. There is also a GNU project with a file that doesn't display the standard notice (as I've pointed out via chat). In fact, it doesn't even say it's GPL: http://pastebin.com/m25522567 (from wdiff). I'd concur with you that the above are bad. But I am not trying to do any of those things, I'm just trying to make it shorter. And if you look around savannah, there is a plethora of different notices of different sizes and contents. I am not doing anything wrong, so Mario, would you let me post my project?

Luka M. <paxcoder>
Fri 29 Jan 2010 07:27:55 PM UTC, comment #9: 

Everybody at Savannah will ask you to place a license and copyright notice in each non-trivial file (e.g. > 10 lines of code).

If you have no notice yet, it would make sense to do that automatically (sed, preg_match...).

Sylvain Beucler <Beuc>
Fri 29 Jan 2010 06:36:17 PM UTC, comment #8: 

I'm sorry, I'm not going to put 12 lines of notice text in each and every of 47 files - if there is not absolutely necessary. If it were an important project, with as many as 10 files containing code, I would. But I have dozens of small functions each in its own file, and each being self-documented with the description of its purpose in the comments at the top of the file (as per GNU coding style guidelines) - adding 12 more lines to all of those would create clutter (a 564 more lines worth of clutter in total). I am, however, still willing to put the said, or similar one liner into those, and have the whole license text in LICENSE.txt. Also, I would put the standard notice in files in the root of the application, as well as keep it in COPYING.txt. If you don't agree, I would like this task to be assigned to someone else (no offense).

Luka M. <paxcoder>
Fri 29 Jan 2010 02:59:06 AM UTC, comment #7: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 28th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

Hi

We just talked about the GPL headers issue yesterday, me with another
savannah hacker (Karl Berry).

Even if one line like "This file is GPL 3 or later" may be considered
valid in a court, there are a better way: the standard header (The one
adviced inside the GPL).  The standard header has been reviewed by
several people, including lawyers, it is not only valid from the law
viewpoint, but also have serveral other advantages like the ones I
alredy telled you on IRC, it includes warranty disclamer, It tells the
user that he/she has the freedom, and it tells the user the URL of the
licence in the case the distributor have not provided a copy of it
along with the code, and so on...

So, as you haven't stated a good reson to use the one line "header"
other that you pleases, we require you to use the standard header,
wich is better because of tha avobe, and other reasons.

I wait the updated tarball to continue with the registration
processes, if all is ok I will approve the submission, else I will
point you what changes are need.

Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktiTvEACgkQZ4DA0TLic4j0/QCdGjYKxg0zIzSbpikuClQ4b63N
KT4An2tmjHwyZO6TpNUVfS0dy4Zv17Nx
=Kzbe
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sat 23 Jan 2010 04:38:40 PM UTC, comment #6: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 23th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

>If it's enough for a one-liner to cover 10 lines of code, why not a
>whole function?


One line of licencing information is not enough to put something under
the GNU GPL, be it 10 lines of code, one milion or one function.

>If it's a matter of opinion


No, it's a matter of law, Copyright law.  Why you don't want to put
the full licence notice?, I dobut there is a good reason for not do
so.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktbJaYACgkQZ4DA0TLic4iUcgCfah0EBXAnSdyuD5EW/OVlUbKA
zP4AniM8n9D2BCMJhck5QqR1fwpC3epG
=3Kvv
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sat 23 Jan 2010 01:16:03 PM UTC, comment #5: 


>No, I alredy pointed you to the instructions to licence under the GNU GPL 3.


I have read the above in the past. If it's enough for a one-liner to cover 10 lines of code, why not a whole function? If it's a matter of opinion, I'd rather cover files for inclusion with one-liners with copyright and licence reference (I think 12 lines is too much for a 20-lines code). Again, main files will be covered with the whole thing (that which you copy-pasted). I'd include the README in the root also, with licensing info for the images as you suggest. What do you say?

Luka M. <paxcoder>
Sat 23 Jan 2010 03:18:05 AM UTC, comment #4: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 22th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

>I'd be willing to add a full notice to the files in the root
>directory, and a short one-liner to the files in subdirs (those
>containing functions and stuff). Would that be acceptable?


No, I alredy pointed you to the instructions to licence under the GNU
GPL 3.

I saw the project have images, as they can not contain the licencing
information inside you should add a README file enuemerating the
images, and stating it licence, something like:

phpDebate is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

Item status changes:

Stauts -> In progress.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktaagkACgkQZ4DA0TLic4guXQCfdtAlumVLsRxuBP9a1++zDk9p
S3kAnAnk7R2HN+/jQYO1RU7s4J6fA7RT
=+GWS
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Fri 22 Jan 2010 05:51:05 PM UTC, comment #3: 

I'd be willing to add a full notice to the files in the root directory, and a short one-liner to the files in subdirs (those containing functions and stuff). Would that be acceptable?

Luka M. <paxcoder>
Thu 21 Jan 2010 11:17:15 PM UTC, comment #2: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 21th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

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.

Item status changes:

Status -> Ping-ed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktY4IQACgkQZ4DA0TLic4gbuACfTiplIhJjH6+2FeNtlc2Uu+f2
P1AAnA6vjNXHbtDGeQm6FbwRJEh4hc8u
=BJTH
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Mon 11 Jan 2010 06:58:22 PM UTC, comment #1: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

January 11th 2010 en GNU Savannah task 10086: "Submission of
phpDebate"

Hi,
 
I'm evaluating the project you submitted for approval in
Savannah. While doing so I have noticed a few problems which are
described below.

All the files lacks licencing information, check
http://www.gnu.org/licenses/gpl-3.0.html#howto more information, and
update your files.

Regards.

Item stauts changes:

Assigned to -> marioxcc
Stauts -> In progress
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAktLdKsACgkQZ4DA0TLic4hpuACghJ8LSbq8+KtYp2SRnFmcpr6E
ZRMAniF/PYXhgYFiyRNpIpUeQcPPl5IW
=37Kl
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Mon 11 Jan 2010 03:21:07 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: phpDebate
  • System Name:  phpdebate
  • Type: non-GNU software & documentation
  • License: GNU General Public License v3 or later





Description:

Software for multilingual web sites for online debating. Written in PHP, and depending on JavaScript("ajax"), XHTML, CSS - and MySQL for its database (database structure included).


Other Comments:

XHTML/CSS designers welcome (some PHP and perhaps JavaScript knowledge required)


Tarball URL:

http://savannah.gnu.org/submissions_uploads/paxDebate.tar.gz


Luka M. <paxcoder>

 

(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 Beuc (Posted a comment)
  • -email is unavailable- added by marioxcc (Posted a comment)
  • -email is unavailable- added by paxcoder (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
    2010-01-31 marioxcc StatusIn Progress Cancelled
        Open/ClosedOpen Closed
    2010-01-23 marioxcc StatusPing-ed In Progress
    2010-01-21 marioxcc StatusIn Progress Ping-ed
    2010-01-11 marioxcc StatusNone In Progress
        Assigned toNone marioxcc

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code