Project

Process

The fictional "source:jam" language is used to implement the requirements. Real Life languages are the used to come close to the fictional jam language.

Practice oriented use-cases are used, which start from very simple coding, going over to reflection, persistence, gui, editing, metadata, attribution, genericity, packaging, distribution etc.

The Foundation for the evaluation are the requirements which were specified within the Case Project. Additional requirements are created during the progress.

Team

The project is a personal work of Ilias Lazaridis, who

  • provides the (fictional) Jam implementation
  • provides the Perl implementation

Contribute

Any interested parties can use external repositories to provide implementations for languages of their choice. In order to allow people to compare the different languages easily, the jam-file scheme should be followed.

Contact the project to provide an implementation for a language using the project repository. In this case you have to follow strictly the jam files.

You can contribute easily by following the filed tickets and the "source:jam" files.

The SVN location is: http://dev.lazaridis.com/lang/svn

If you need more information about project organization basics, just take a look at the base project. Most things mentioned there are valid within this project, too:

http://dev.lazaridis.com/base/wiki/ProjectOverview

Guidelines

  • As a basic rule, keep any file autonomous (e.g. the file runs stand-alone).
  • Follow strictly the file/path scheme of the "jam" language.
    • do not add files/folders, except absolutely necessary
  • Do not add files for IDE's (command-line and text-editor exists, IDE's do not)
  • Provide the implementation of the requirements - do not discuss them!

Use the following commit messages, which will trigger an automation which add's comments to the tickets (or close the tickets): 

re #12, description of change
closes #12, description of change

Whenever possible, reference a ticket-number when altering the repository.

An implied Joint Copyright Assignment is used for files going into the project repository.

This means practically:

  • You keep the copyright to your contributions, but assign a joint copyright to Ilias Lazaridis, simply by leaving the copyright notice at the header intact. There's no need for a signed agreement.

For more information about Copyright, see: