Get involved

We are always looking for people who are selfmotivated and willing to contribute. You do not have to be a programmer to help the project. There are a lot of different tasks you can get involved with. Donations [more] are another very important action to contribute to the project.

As a first active step, we recommend you to join the iometer-user mailing list [more]. Here many of the iometer users are discussing different topics and issues. Joining the discussion, learning from others as well as helping others is the first step forward which helps the project a lot!

A next step is to join the iometer-devel mailing list [more]. Here the project members are discussing the different project related issues (today most communication is still direct email between the involved people). But you are also more then welcome to contact the project members directly.

Here is a selection of some tasks for which we are looking for help:

Coding
status task
started (1, 2)
  • Code Cleanup
    1. Consolidate the different code and header files
    2. Consolidate and decouple the different global defines
ongoing
  • Tackling Bug Reports [more]
ongoing
  • Tackling Feature Requests [more]
none
  • Development of an Hardware Abstraction Layer (hiding CPU, OS and OS family specifics)
none
  • Porting to different operating systems and hardware platforms
    1. Operating System: AIX
    2. Operating System: (Free|Net)BSD
    3. Operating System: IRIX
    4. Processor: Alpha
    5. Processor: MIPS (R10000 etc)
    6. Processor: PowerPC
started
  • Iometer GUI for Non-Windows (Java)

 

Testing
status task
none
  • Building an QA testsuite (using dd and stackthru/netperf as base line for simple Iometer configurations)
none
  • Testing new builds / releases (especially combinations without prebuild package)
    1. Solaris (on SPARC)

 

Documentation
status task
started
  • Keeping the Users Guide up to date
none
  • Building an FAQ document (based on the work of Richard Riggs)

 

Others
status task
none
  • Analyse source code and describe data flow etc in the Developers Guide
none
  • Building a rich set of sample ICF's (synthetic and real world work load)
none
  • Setup a results database (simular to netperf.org)