File Name
<body>
<H1>Swarm App Archive</H1>
<p>
<H2>How to contribute</H2>
To submit a Swarm application that you want to share through this
ftp repository, please follow the file naming
conventions of the LSM archiving system, with just a little wrinkle to
match the Swarm needs, as described in this document: <a
href="SwarmLSMNames.html">SwarmLSMNames.html</a>
<p>
Please submit an lsm file with your project. An lsm file is a flat
text file that gives author/version information. There is a template
for lsm files here <a href="LSM-TEMPLATE">LSM-TEMPLATE</a> and there
is a longer, older description of the LSM scheme here <a
href="LSM.README">LSM.README</a>
<p>
<H2>What you can get here</H2>
Programs are divided according to the language in which they are
written. So far, we have apps in Java and Objective-C. Within those
categories, programs are further divided as follows.
<p>
<blockquote>
<ol>
<li>sdg. Indicates that this is written by SDG or that our members
are dedicated to making sure it will run with current versions of
Swarm. If a program is in here, it means that some SDG board member
is willing to try to make it work against newer editions of Swarm, if
it does not already.
<li>contrib. These are contributions from Swarm
users, many of which work. :) Formerly, we were separating contrib
into two subsections, "evaluated" and "anarchy". We are not making
that distinction now. Some of these were written by Swarm Development
Team members in the past, and they are not in the sdg category because
nobody is making a "blood oath" to maintain them (keep them up to
date, perform bug fixes, etc). In the contrib directory, one finds
many workable, useful models.
</ol>
</blockquote>
<p>
Please note as well that there are directories called
<b>obsoleted</b> that hold older versions of these programs.
There may also be directories named <b>testing</b>.
Guess what might be in there :)
<p>
Last updated November 15, 2001
<br>
Paul Johnson <pauljohn@ukans.edu>
</body> </html>