taskSavannah Administration - Tasks: task #5917, Submission of ThemeX/Westgen...

 
 

task #5917: Submission of ThemeX/Westgen Site-Wide Template Engine

Submitted by:  Brian <brianez21>
Submitted on:  Fri 22 Sep 2006 08:37:18 PM UTC  
 
Should Start On:  Fri 22 Sep 2006 04:00:00 AM UTC Should be Finished on:  Mon 02 Oct 2006 04:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Stephan Peijnik <sp>
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)

Tue 10 Oct 2006 08:15:19 PM UTC, comment #8: 

Hi Brian,

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

Regards.

Stephan Peijnik <sp>
Project MemberIn charge of this item.
Mon 09 Oct 2006 08:17:07 PM UTC, comment #7: 

Hi again,

> First of all, the license you've included in your tarball is outdated.

Sorry about this. Attached is a new archive with the fixes you stated.

> Secondly, your submission and your license headers in the tarball state that you are licensing your project under the GPLv2 or later, is this still correct?


I am ok with using the GPL v2 and later.

> Thirdly, there is a license missing for the binary files (ie. pictures, etc.) in your tarball.

I added a GRAPHICS file.

> Please include a verbatim copy of the LGPL in the tiny_mce subdirectory.

I created a COPYING file.

Thanks,
Brian

Brian <brianez21>
Mon 09 Oct 2006 03:15:29 PM UTC, comment #6: 

Hi Brian,

I have now evaluated the tarball you submitted and I noticed a few problems. These problems are described below.

First of all, the license you've included in your tarball is outdated. The address of the FSF has changed and you should fetch a fresh copy from http://www.gnu.org/licenses/gpl.txt. This will also fix a problem with the license file itself, as your version is missing the last section, 'How to Apply These Terms to Your New Programs'. Please also note that whilst keeping the license in a file named 'license.txt' is okay, it is recommended to name that file 'COPYING'.

Secondly, your submission and your license headers in the tarball state that you are licensing your project under the GPLv2 or later, is this still correct? You mentioned that you wanted to use the GPLv2 only. In fact, we would like you to use the GPLv2 or later. As I mentioned before, licensing under the "GNU GPL v2 only" is problematic.

The reason for this is that when we publish GPL v3, it will be important for all GPL-covered programs to advance to GPL v3. If you don't put this in the files now, the only way to port your program to GPL v3 would be to ask each and every copyright holder, and that may be very difficult.

Thirdly, there is a license missing for the binary files (ie. pictures, etc.) in your tarball. Please add a README file in the same directory containing the copyright and license notices. Check http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices for further information.

The GPL FAQ explains why these procedures must be followed.

Another thing I've noticed is that the tiny_mce subdirectory is missing the LGPL license text. Please include a verbatim copy of the LGPL in the tiny_mce subdirectory. The easiest way to achieve that is to simply copy a 'clean' version of the whole tiny_mce distribution into the subdirectory of your project.

If you are willing to make the changes mentioned above, please provide us with an URL to an updated tarball of your project.  Upon review, 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.

Stephan Peijnik <sp>
Project MemberIn charge of this item.
Sat 07 Oct 2006 11:49:14 AM UTC, comment #5: 

Hi Brian,

ad 'since other popular GPL software can do the same thing':

First of all, it's not an issue of 'can' or 'can not', technically speaking, but rather of 'being allowed to' due to the license terms.

Please have a look at http://www.fsf.org/licensing/licenses/gpl-faq.html#LinkingWithGPL, you should find information about this issue there. As for the kernel: there are various views about the topic, ie. if loading a proprietary kernel module results in a combined work of the kernel and the module in question. If that is the case it is a clear license violation and renders all rights granted through the GPL void. However, as I said, there are various views on that topic. Personally speaking, I do believe this is a license violation and therefor have strong feelings about issues like that.

Another thing you might want to have a look at is http://www.fsf.org/licensing/licenses/gpl-faq.html#UnreleasedMods,
which explains how modified versions of a GPL'ed program do not have to be distributed, if they stay in-house. This could lead to confusion that people modified some GPL'ed program and make it look like they've loaded/added proprietary code, but in fact they've added modifications under the terms of the GPL and have simply never distributed those.

I can't comment on Wordpress though, but loading modules/addtional scripts can be seen as dynamic linking and thus would also mean a license violation.

I do recommend that you read the whole GPL FAQ at http://www.fsf.org/licensing/licenses/gpl-faq.html as it may contain a few answers to your question.

I'll let you know once I've reviewed the tarball.

Regards.

Stephan Peijnik <sp>
Project MemberIn charge of this item.
Fri 06 Oct 2006 12:20:06 AM UTC, comment #4: 

Hi again,

I am willing to release the code as fully-GPL'ed Free Software. The only issue is that the program CAN and WILL load external modules. I don't see how this violates the GPL, since other popular GPL software can do the same thing (for example, Wordpress and the Linux kernel).

Anyway, attached is a copy of the not-fully-functional software.

Thanks,
Brian

Brian <brianez21>
Thu 05 Oct 2006 08:31:35 PM UTC, comment #3: 

Hello Brian,

Free Software in itself implies that the program is what people tend to call 'open source software'.
From a legal point of view there are various problems 'linking' (ie. loading a module of) proprietary code into a GPL'ed program. This is strictly forbidden by the GPL itself and hence is a license violation. However, do you really need to dual-license your program?

We would really like you to use the 'GPLv2 or later' clause. The main intention behind using this is that it simplifies the process once the GPLv3 is released. This means if you are not using the 'or later' clause, you would have to ask every copyright holder of every piece of sourcecode for permission, which could and for sure would cause problems.
If you want to review the draft of the GPLv3, please go to http://gplv3.fsf.org/. Also, if you do have any concerns, feel free to state them. Basically, the GPLv3 is only an update to the GPLv2, keeping the very idea behind the license the same and only rewording or elaborating a bit more on some problems that came up since the relase of version 2 (such as DRM and software patents).
Please also have a look at http://www.gnu.org/licenses/gpl-faq.html#VersionTwoOrLater, which contains a lot of information on why we insist on using 'v2 or later'.

Now about the legal issues we would be checking for. These include:

Checking of both license and copyright header for presence and validity.
Checking for presense of the license text of the license used.

Basically this is done in order to ensure legal correctness and hence validity. In short it is meant to also ensure that your Free Software program stays such and cannot be made proprietary software due to missing legal correctness of, for example, a copyright header.

Last but not least, Tiny-MCE, if licensed under the LGPL, should not pose a problem.

I hope this clarifies everything.

Regards,

Stephan

Stephan Peijnik <sp>
Project MemberIn charge of this item.
Mon 02 Oct 2006 02:01:14 AM UTC, comment #2: 

Hello Stephan,

(1) The ThemeX/Westgen project is both Open Source and Free Software. However, the project has the feature to load third party modules which may or may not be Open Source or Free Software.

(2) I will license the code under the GNU GPL v2, but I am not sure about the "or later" clause. I will have to review the terms of the GPL v3 when it is released.

(3) What type of legal issues will you be checking the source code for? Also, I am placing the copyright notice at the top of all the files. Development on the project was started, and I will see if I can get it posted online for further review.

Also, one of the other pieces of software required has been changed. FCKeditor has been replaced by Tiny-MCE. This should not be a problem because Tiny-MCE is also released under the LGPL.

Regards,
Brian

Brian <brianez21>
Sun 01 Oct 2006 08:14:50 PM UTC, comment #1: 

Hi,

I'm evaluating the project you submitted for approval in Savannah. Whilst evaluating your submission I noticed a few problems which are described below.

First of all, 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.

Second thing I noticed is that you are planning to dual-license your project. I'd like you to read https://savannah.gnu.org/maintenance/ProprietaryUseOfFreeSoftware which contains basic information about this 'issue'. In fact, we'd like you to release your project under a Free Software License only, due to the ethical and social problems proprietary software comes with. Would you agree on licensing your project under the GNU GPL v2 or later only, instead of using a dual-licensing scheme?

The third thing is that we'd like you to include a (perhaps temporary) URL pointing to the source code. Alternatively, you can forward the code to me by email or attach it to this tracker.

We wish to review your source code, even if it is not functional, to catch potential legal issues early.

For example, to release your program properly under the GNU GPL you must include a copyright notice and permission-to-copy statements at the beginning of every  copyrightable file, usually any file more than 10 lines long.  This is explained in http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch potential omissions such as these.

Note that sending code to our repositories is a release, since the code will then be publicly available through anonymous access.

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.

Stephan Peijnik <sp>
Project MemberIn charge of this item.
Fri 22 Sep 2006 08:37:18 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):

  <https://savannah.gnu.org/siteadmin/groupedit.php?group_id=8793>

REGISTRATION DETAILS

Full Name:
----------
  ThemeX/Westgen Site-Wide Template Engine

System Group Name:
-----------------
  westgen

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

License:
--------
  GNU General Public License V2 or later (+ dual licensing)

Description:
------------
  This project, titled "ThemeX/Westgen Site-Wide Template Engine" is an Open Source (GPL v2) Web-based content management system written in PHP. It was created with a Web Designer's job in mind. The backend of the program will piece together web pages from the pre-configured files it reads and display them to the viewer. The administration backend allows the end-user to modify the web pages and other files included on the web site. It is modular and includes the following features by default:

  • File-management
  • Page editor
  • Text editor
  • Gallery
  • Audio Player

There is no source code online for this project yet, but planning is currently underway.

Other Software Required:
------------------------
  Unix-based web server
The PHP Hypertext Preprocessor (PHP license v3)
FCKeditor, The text editor for the Internet (LGPL v2.1)
XSPF Web Music Player (BSD license)

Brian <brianez21>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #10933:  wgtx-0.9pre1-alpha3d2.tar.bz2 added by brianez21 (277KiB - application/octet-stream - Westgen/ThemeX 0.9-pre1-alpha3d2)
file #10903:  wgtx-0.9pre1-alpha2.tar.bz2 added by brianez21 (266KiB - application/octet-stream - Westgen/ThemeX version 0.9pre1-alpha2)

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

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

Date Changed by Updated Field Previous Value => Replaced by
2006-10-10 sp StatusWait reply => Done
    Open/ClosedOpen => Closed
2006-10-09 brianez21 Attached File- => Added wgtx-0.9pre1-alpha3d2.tar.bz2, #10933
2006-10-09 sp StatusIn Progress => Wait reply
2006-10-07 sp StatusWait reply => In Progress
2006-10-06 brianez21 Attached File- => Added wgtx-0.9pre1-alpha2.tar.bz2, #10903
2006-10-01 sp StatusNone => Wait reply
    Assigned toNone => sp

Back to the top


Powered by Savane 3.5