Access Keys:
Skip to content (Access Key - 0)

How to become a Committer

In order to become a contributor you will need to:

  1. Have a RiverMuse account - sign up here
  2. Have been actively and positively involved in supporting the RiverMuse community at a discussion and contribution level
  3. Been successfully nonimated by an existing RiverMuse Community Board member or following an emailed request to become a Committer sent to board@rivermuse.com

RiverMuse Committer Guide

We'd love to see you showing the commitment that means we can make you a committer and have you join in. The ways that people get involved in open source are pretty varied, but a common course might go something like this:

  • You see functions and features that need to be added, or parts of the code that do not work quite right
  • You investigate the existing code, becoming more familiar with it along the way
  • You bring new ideas to the community and start discussion threads on the RiverMuse forums
  • You contribute positively to the discussion of these ideas (yours and others) - gaining knowledge of what RiverMuse is all about as you do so and also getting know to the community
  • At some point, you propose a contribution that gets accepted into the RiverMuse code base
  • Iterate the above a few times, perhaps looking at bigger and bigger chunks of code as you gain more understanding
  • At some point, when it is evident that you're a serious contributor, you can get nominated for committer status and voted on by the RiverMuse Community Board, and then be able to post the changes directly yourself. Alternatively you can initiate the process yourself by emailing a request to the community board at board@rivermuse.com.

1. Committer Approval Process

This process describes the RiverMuse (Core) community governance process put in place to handle the nomination and appointment of Committers.

Description

The RiverMuse Core product is Open Source encouraging contribution from community members and where appropriate would hope they will become Committers. The process has been in part developed based on the practices of the Eclipse Forum and the Apache Software Foundation; both of which have a good reputation as Open Source communities.

Start Process

The process starts when an OSS Professional visits RiverMuse.org and decides to become an active member

Register on RiverMuse

Register as a member on RoverMuse.org

Performers

  • User

Become Active Member

Start making positive contributions on forums helping to provide, develop and shape ideas within the community

Performers

  • User

Contribute Code

Through the defined Contributor Process the user contributes changes and enhancements to RiverMuse Core

Performers

  • Contributor

Nominated to Become a Committer

After a period of active participation within the community and positive contributions to RiverMuse Core, an existing Community Board Member may decide the time has come to make a Committer nomination to the RiverMuse Community Board

Community Board Approval

At an appropriate point, the RiverMuse Core Community Board review the nominations for Committers and approve or reject as agreed.

GATES

  • Nomination Approved
  • Nomination Rejected

Nomination Approved

Nomination Rejected

2. PARTICIPANTS

User (Role)

A 'User' is a community type of member who uses the deliverables from the RiverMuse community. They do not provide direct contributions to the product but do provide feedback and evidence of usage.

Contributor (Role)

A 'Contributor' is a type of member of the RiverMuse community that makes contributions to the community. They can download from SVN but must submit any contributions back through a Committer.

Committer (Role)

A 'Committer' is a trusted of member of the RiverMuse community who can commit changes to SVN. They act as an approver for contributions from Contributors

Community Board (Role)

The Community Board is made up of three senior members of the RiverMuse community . They have the responsibility for setting the strategy and roadmap for the community.

The Board also acts as the body empowered to resolve disputes within the community that cannot be resolved at the project level.

Adaptavist Theme Builder (3.3.5-M4-SNAPSHOT-conf210) Powered by Atlassian Confluence 2.10, the Enterprise Wiki.