Elm is currently developed by a group of volunteers. Each volunteer is asked to contribute by not only adding features, but by also writing documentation and fixing bugs. Knowledge of UNIX and the C programming language is required.
Developers need electronic mail access to tigger.itc.virginia.edu to communicate with the other members of the group via a private mailing list. In addition access either via ftp or anonymous uucp is required to retrieve new releases. Changes are submitted in patch format via electronic mail to the Elm Coordinator. It is the coordinators job to merge them into the development tree and build new releases.
All members of the Elm Development Group are automatically members of the Elm Testing Group.
Membership in the Elm Development Group is open anyone who wishes to join.
Once a new release or an integrated patch set has been developed, it is released to the Elm Testing Group for beta testing. While alpha testing is performed within the Elm Development Group, there is a need for a wider audience for the beta test.
This group of volunteers is responsible for performing the beta testing. This entails compiling the new patches when they are distributed to the group and reporting any problems found. It is not required for members of this group to submit corrections to the problems they uncover, but it is very helpful if they can diagnose any problems. Especially those due to portability issues with the different flavors of UNIX.
Testers need electronic mail access to tigger.itc.virginia.edu to communicate with the other members of the group via a private mailing list. In addition access either via ftp or anonymous uucp is required to retrieve new releases.
Mail your message to email@example.com with the body of the message containing a subscribe command as either:
SUBSCRIBE elm-test Your-Email-Address or SUBSCRIBE elm-dev Your-Email-Address
Join the Elm Lists Now