taskSavannah Administration - Tasks: task #5208, Submission of Cashews Tools

 
 

task #5208: Submission of Cashews Tools

Submitter:  Andrew John Hughes <gnu_andrew>
Submitted:  Thu 26 Jan 2006 03:52:13 PM UTC
   
 
Should Start On:  Thu 26 Jan 2006 12:00:00 AM UTC Should be Finished on:  Sun 05 Feb 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 08 Feb 2006 11:03:06 PM UTC, comment #5: 

Hello.


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




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

Regards.

Sebastian Wieseler <kickino>
Wed 08 Feb 2006 08:27:48 PM UTC, comment #4: 

Okay, I'll try and clarify things a bit, as I seem to have left things a bit unclear.

The new project should contain the code in the CVS of the current project with the exception of the contents of cashews/src/nongnu/cashews/eclipse.  This directory contains an Eclipse editor plugin (or the beginnings of) which originally meant that the project needed to be dual-licensed (as GPL code can't be linked with Eclipse).

The original work was completed as part of an academic project, which is now over (as of last June to be exact).  However, we would hope to be able to maintain the more successful parts of this for future development.

Thus, if possible, I'd like:

  • the cashew-s-editor project to be left as is.  Primarily, this is so it remains representative of the results of the above-mentioned project.  It also retains the possibility that someone may want to pick up and run with the editor stuff at a later date.


  • a new project to be created, cashews-tools (the concern of this submission) which contains the backend material that was created as part of this project.  As author of this code, I'd like to be able to go on maintaining this as a free project.  Hopefully, others will also be able to contribute in the future as well.  Thus, this should contain just myself as the only member and maintainer of the new group, and the contents of the previous repository, with the exception of the Eclipse code referenced above.  If necessary, I can add this to the new repository myself.


The proposal is less to do with a new venture, than with providing a more accurate framework for future development on this part of the project.

Hope this clears things up.  To reiterate, all code in the previous project, with the exception of cashews/src/nongnu/cashews/eclipse, should be considered part of the new project.

Thanks.

Andrew John Hughes <gnu_andrew>
Wed 08 Feb 2006 07:47:01 PM UTC, comment #3: 

Hello.

Do you mean ' Code already exists within an existing Savannah project (http://savannah.nongnu.org/projects/cashew-s-editor).'?


If yes, I don't want to review a whole existing Savannah project and you extract then the code you needed. You see my point?

On the other hand if you want me to review an existing SV project, please tell us only. ;-)

If no, I'm sorry.

Regards,

Sebastian Wieseler <kickino>
Wed 08 Feb 2006 11:43:42 AM UTC, comment #2: 

The URL is in the original submission.

Andrew John Hughes <gnu_andrew>
Wed 08 Feb 2006 10:39:56 AM UTC, comment #1: 

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

Please include a (perhaps temporary) URL pointing to the source code.
The description you gave when registering will not be read by the general public.
If you are still concerned with privacy, however, you can forward the code to me by email.

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 GPL you must include a copyright notice and
permission-to-copy statements at the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch potential omissions such as these.



Regards,

Sebastian Wieseler <kickino>
Thu 26 Jan 2006 03:52:13 PM 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.gnu.org/admin/groupedit.php?group_id=8312>


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

Full Name:
----------
  Cashews Tools

System Group Name:
-----------------
  cashew-s-tools

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

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

Description:
------------
  The purpose of this project is to facilitate the composition of semantic web services. It consists of at least two parts, of which this is one.
 
 This is a set of tools which enable the Cashews engine to be utilised from within the Java programming language.  Interoperability is performed by communicating, via a SOAP 1.1-based web service, with the engine which runs using the functional language, Haskell (see http://savannah.nongnu.org/projects/cashew-s-engine).  At some point, the code may be expanded to make this dependency optional, but at present, this is the only engine implementation.

 Code already exists within an existing Savannah project (http://savannah.nongnu.org/projects/cashew-s-editor).  The purpose of this additional project application is to separate the lower-level bindings to the engine from the UI level tool (which is not currently in active development).

Currently, sufficient Java code exists to represent a Cashews process and serialize it using the provided XML serializer.  Pertinent development targets at present including cleaning up this code and developing a deserializer.

The primary platform for development of this work is GNU/Linux with the GNU Classpath generics branch and associated tools providing the Java framework.  This is the primary testbed for this work, although it should work in alternate Java development environments (in theory).

The web site, http://www.dcs.shef.ac.uk/~andrew/, lists a number of publications which are pertinent to this topic.


Other Software Required:
------------------------
  The code depends on a Java development environment.  As noted above, the primary development environment is the GNU Classpath generics branch with a Free VM and compiler.  Currently, the latter is limited to ecj, as the only available Free Software compiler supporting the 1.5 language features.  With the release of gcjx, this will change.
The bindings have no UI, so Swing is not an issue.  If the need for such a UI does arise, then Swing is unlikely to be used anyway (with the preference being for a solution that better fits into existing Free Software environments)

Other Comments:
---------------
  This project is related to two existing Savannah projects: cashew-s-engine and cashew-s-editor.  The initial codebase will be derived from the latter.
The presumption is that these tools can now be licensed solely under the GPL, as they are separate from the Eclipse plugin and there is no intention for the two to interact at present.  This issue should hopefully be rectified fully by the GPLv3 when it is released.


Andrew John Hughes <gnu_andrew>

 

(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 4 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-02-08 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2006-02-08 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-caa5.
Corresponding source code