		========= jal Maintainers =========

This is the list of individuals responsible for maintenance and update
of the jal project.  This includes the compiler (jal) and the libraries 
it uses.  

The home page for jal is:

  http://jal.sourceforge.net

and patches should be sent to:
  
  https://sourceforge.net/projects/jal/

or:

  Eur van Andel <eur@fiwihex.nl>
  
with "[Patch]" as part of the subject line.

      --------- Blanket Write Privs ---------

The following people have permission to check patches into the
repository without obtaining approval first:
		
  Eur van Andel <eur@fiwihex.nl> (head maintainer)
  Wouter van Ooijen <wouter@voti.nl>
  Javier Martínez <japus11@terra.es>

      --------- Maintainers ---------

Maintainers are individuals who are responsible for, and have
permission to check in changes in, certain subsets of the code.  Note
that maintainers still need approval to check in changes outside of
the immediate domain that they maintain.

If there is no maintainer for a given domain then the responsibility
falls to the head maintainer (above).  If there are several
maintainers for a given domain then responsibility falls to the first
maintainer.  The first maintainer is free to devolve that
responsibility among the other maintainers.

  jal library	   Eur van Andel <eur@fiwihex.nl>
  jal docs         Eur van Andel <eur@fiwihex.nl>
  jal config       Craig Franklin <craigfranklin@comcast.net>

     --------- Write After Approval ---------

Individuals with "write after approval" have the ability to check in
changes, but they must get approval for each change from someone in
one of the above lists (blanket write or maintainers).

  FIXME: Insert names.
  Mark Gross <mark@thegnar.org>

     -------------  Obvious Fixes -------------

Fixes for obvious mistakes do not need approval, and can be checked in
right away, but the patch should still be sent to Eur van Andel.
The definition of obvious is a bit hazy, and if you are not sure, then
you should seek approval first.  Obvious fixes include fixes for
spelling mistakes, blatantly incorrect code (where the correct code is
also blatantly obvious), and so on.  Obvious fixes should always be
small, the larger they are, the more likely it is that they contain
some un-obvious side effect or consequence.

     -------------  Guidelines -------------

The following are guidelines for those maintaining jal.

1.  All files shall use ISO file format.  All files lines should terminate
    with a LF (0xa).
2.  No line shall exceed 78 characters.
3.  No tab characters shall be used.
4.  The filenames must be lower case alphanumeric characters, underscores("_"),
    and periods (".").
5.  The natural language of the package is English.

     -------------  Release Procedure -------------

Jal releases shall be made as often as possible.  The following outlines
a basic procedure to accomplish this:

1.  Update ChangeLog to reflect changes and the release.
2.  Update the version in configure.ac and run /usr/local/bin/autoconf.
3.  Command "make" in the jal root.
4.  Change to /jal/testuite and run the test scripts.  Verify the output.
5.  change to jal root and do a cvs commit to update the configure and 
    config.ac files in the cvs.
5.  Change to the working directory were jal was checked out.  Command
    "cvs tag jal-XX_YY_ZZ jal", where XX, YY, and ZZ are replaced by the 
    appropriate version.
6.  Command "make distcheck" to generate the source distribution.
7.  Command "make dist-zip" to generate a zipped version of the same source.
8.  Follow the sourceforge procedures to generate a new file release.  Add
    the new source distribution to the new release.

