Project ArgoUML Members with Responsibilities

The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.26 release (alphabetical order):

The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.24 release but not (yet) towards the 0.26 release (alphabetic order):

The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.22 release but not (yet) towards the 0.24 release (alphabetic order):

The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.20 release but not (yet) towards the 0.22 release (alphabetic order): The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.18 release but not (yet) towards the 0.20 release (alphabetic order): The following people are committed to advancing the ArgoUML project and have been doing work towards the 0.16 release but not (yet) towards the 0.18 or 0.20 releases (alphabetic order): The Responsibilities are defined and delegated by the Project leader. If you would like to assume the responsibility for some area, please discuss it with him. You are most welcome! A Specialty is provided as information.

You can also look at the whole list of involved people.

Expectation on persons with a specific responsibility

This is the definition of what the Project Leader (Linus Tolke) expects from you when you have a responsibility in the ArgoUML project. It is a complete list of all delegated responsibilities.

For all roles and responsibilities it is expected:

Responsibility: Developer role

This role is registered by the Tigris framework.

Responsibility: Editor of the User FAQ

Responsibility: Mailing list moderator

Responsibility: Back-up moderator of a mailing list

Responsibility: Member administrator

Responsibility: Editor of the Cookbook

The Cookbook is the document that contains information for the developers of ArgoUML and modules.

Responsibility: Release Responsible for all Releases

If the Release Responsible for all Releases does not appoint a Release Responsible for a specific release that means that he will take care of it himself becoming the Release Responsible for that release.

A Release Responsible for a specific release has the following responsibilities:

Responsibility: Editor for the User Manual and Quick Guide

Responsibility: Subsystem responsible

This role is registered by the Tigris framework (in the Issuezilla settings).

Other things that would be good if you do but not required are:

Responsibility: Quality Engineer

Other things that would be good if you do but not required are:


Last modified: $Date$
Please send any questions or comments about this web page or its content to Linus Tolke.