Login | Register
My pages Projects Community openCollabNet

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:

  • that you suggest improvements of the role you have and how it is defined in this page, and
  • that you notify the project leader if, for any reason, you feel that you don't want that responsibility any more or when you feel that you cannot fulfill your responsibilities.

Responsibility: Developer role

This role is registered by the Tigris framework.

  • Keep yourself updated on the current development, tools, policies, rules and coding standards used in the project so that you can do commits that agree with the direction of the project.
  • When you receive mail from people that want to contribute to the project, you help them commit their contributions or suggest that they should contact someone else.
  • Among the people sending you contributions you keep an eye out for new developers and suggest them to the Project Leader.

Responsibility: Editor of the User FAQ

  • Monitor the Users' mailing list.
  • Have name, email-address and Issuezilla id stated so that contributions and suggestions can be sent to the right person.
  • Take part in all discussions on the contents and format of the User FAQ.
  • Add things found on the Users' mailing list and contributions to the User FAQ.
  • Remove things from the User FAQ that are no longer interesting.
  • Publish new versions of the User FAQ when changed.

Responsibility: Mailing list moderator

  • Receive mails sent to the list that are to be approved.
  • Approve or reject these mails (based on the agreed policy for the list in question).
  • Reminding people that sending unrelated things on the mailing list is discouraged (especially "Please unsubscribe me"-messages).
  • Take part in the discussions on policy for the list in question that should be carried out on the list.
  • If needed, publish the agreed policy.

Responsibility: Back-up moderator of a mailing list

  • Monitor the mails sent to the list owner and make sure that the moderators are doing their job correctly.

Responsibility: Member administrator

  • Approve Observer role requests.

Responsibility: Editor of the Cookbook

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

  • Monitor the Developers' mailing lists for things that would fit into the Cookbook.
  • Continuously improve the contents and layout of the Cookbook.
  • Take part in all discussions on the contents and purpose of the Cookbook.
  • Have name and email stated in the Cookbook so that all potential contributors know where to send their contributions.
  • Accept contributions without DocBook mark-up.
  • Publish the Cookbook on the web site after each substantial change.

Responsibility: Release Responsible for all Releases

  • Decide release dates and contents for all upcoming releases. This is done in agreement with all active developers to fit their personal plans on a level of detail decided by the release manager.
  • Be responsible for the release process and tools. (Appoint persons to design, implement, and improve the release process.)
  • Appoint the Release Responsible for each release.

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:

  • Decide on changes in release dates and contents.
  • Coordinate testers and other helpers to do the work.
  • Doing the actual release work.
  • Close RESOLVED or VERIFIED issues a time after the release.

Responsibility: Editor for the User Manual and Quick Guide

  • Define the contents and organization of the User Manual and Quick Guide.
  • Take part in all discussions on the contents and format of the User Manual and Quick Guide.
  • Define and implement how the User Manual and Quick Guide are to be updated. (i.e. who does the updating and when, how is the quality assurance organized, who does the reviewing,...).
  • Default owner of all issues allocated on Documentation. (i.e. responsible for the triage of all issues that are allocated on Documentation).
  • Decide how the User Manual and Quick Guide are developed. This includes organizing all contributors in this area and leading the work.
  • Decide how and when the User Manual and Quick Guide are published (discussion with release responsible how this is related to release of the ArgoUML product).

Responsibility: Subsystem responsible

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

  • Monitor all work on that subsystem.
  • Have the last say about how the subsystem is designed.
  • Have a clear view of how the subcomponent is related to the source (in the repository) and the definition of packages, modules, subsystems, and sub-projects within ArgoUML.
  • Discuss this relation and updates to the subsystem's Description of responsibilities and provided functions in the Cookbook and the subcomponents description in Issuezilla to better reflect this with the System Architect (Project leader).
  • Default owner of all issues allocated on the Issuezilla subcomponent, for that subsystem. Because of this it is important to mark the issues as available for anyone to work with. This is currently done by assigning them to issues@argouml.
  • Make sure that all issues allocated on that subsystem are in fact problems (or things to do) within that area so that issues don't incorrectly land in that subcomponent.

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

  • Keep the decided design description of the subsystem in the Cookbook up to date with the current design.
  • Lead the team working in the area of that subsystem (if any).
  • Check the priority of all issues so that it is correct.
  • Investigate to make sure that each issue is understood. This involves requesting new information from the reporter.
  • Work with the issues on that subsystem.

Responsibility: Quality Engineer

  • Lead the work in changing the processes.
  • Have the last say about the contents of the processes.
  • Maintain the processes documentation in the Cookbook (Chapter 9).
  • Lead the work in defining the quality level of the code.
  • Have the last say about the quality level.
  • Maintain the Standards for coding in ArgoUML in the Cookbook (Chapter 7).
  • Maintain the settings for the tools that helps us adhere to the Standards for coding in ArgoUML. (argouml/tools/checkstyle, argouml/tools/eclipse, argoumlinstaller, argouml-gen).
  • Decide how the adherence to the Standards for coding in ArgoUML and the quality level of the code are to be monitored and what corrective actions are to be taken and when (in agreement with the release responsible for any affected upcoming release).
  • Communicate the decisions of changes in the processes and quality level to the development community.

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

  • Maintain the description on how to set up the development environment (Chapter 2 in the Cookbook).
  • Do the actual monitoring of the adherence to the Standards for coding in ArgoUML and the quality level of the code.

Last modified: $Date: 2011-05-23 13:15:13 -0700 (Mon, 23 May 2011) $
Please send any questions or comments about this web page or its content to Linus Tolke.