RMoX developers

[ techdocs | mailing lists | source repository | trac | contributing ]

Technical documentation

Currently spread around a bit:

• Design overview: provides a high-level overview of RMoX's concurrent design.
• RMoX reference: reference generated using occamdoc from the RMoX sources (partial/incomplete).

• RMoX config and sys-console: some brief notes on configuration and the "system console".
• RMoX supported devices: incomplete list of supported hardware devices.
• Building RMoX: Adam's guide to building RMoX from source.

Mailing-lists

The following mailing lists are likely to be of interest to RMoX developers, and anybody interested in contributing to the project.

• rmox-announce: RMoX announcements (low traffic)
• rmox-dev: RMoX general development discussion (medium traffic)
• rmox-svn-commits: RMoX subversion commit mailing-list (high traffic)

Source-code repository

The subversion repository for RMoX is hosted on CS-projects at Kent. You can browse or check-out the repository here: http://projects.cs.kent.ac.uk/projects/rmox/svn/rmox/trunk/. The recommended approach is to use subversion, e.g.:

bash:~/oos/$ svn co http://projects.cs.kent.ac.uk/projects/rmox/svn/rmox/trunk rmox

That will grab the latest copy of the RMoX source-code and put it in the directory 'rmox'. You can keep up-to-date by running subversion update inside the 'rmox' directory:

bash:~/oos/rmox/$ svn up

RMoX trac

A trac instance for RMoX is maintained on CS-projects here: http://projects.cs.kent.ac.uk/projects/rmox/trac/. Quick links:

• Project roadmap.
• Active tickets.
• All tickets (by milestone).

Contributing to RMoX

To be able to contribute to development on RMoX (code, testing, documentation, etc.), you'll first need a CS-projects account. To get one of these, fill in the form here: https://projects.cs.kent.ac.uk/newuser. Once that's done, mail Fred with your CS-projects username and ask to be added to the RMoX project.