The MuleForge Hosting Environment

The MuleForge Project Catalogue (MFPC)

• The MFPC is a project in JIRA.
• Each individual MuleForge project is represented as an issue in MFPC. Therefore, when a new project is proposed, a new issue is created within the MFPC JIRA project.
• Each issue (therefore MuleForge project) has a number of properties associated with it. These are:
  • Project name
  • Summary (which should hold the same value as the project name)
  • Project description
  • Project status
  • Project category
  • Project maturity
  • Project URL (This is assigned by the MuleForge administration team when the project is created.)
  • Download URL (This is used when producing a project release.)
  • Has despot (This indicates whether the project currently has an owner.)
  • Has documentation (This indicates whether documentation was written on the homepage of the project.)
  • Supported Mule versions
  • Contributor name and email address
  • License (One of Apache, BSD, CPAL, MPL, LGPL)
  • Consent to Contributor Agreement
  • Legacy CLA (This indicates whether the contributor has signed a paper-based License Agreement, applicable only to legacy projects.

OpenXource Xircles

• Xircles is used to handle the administration of MuleForge projects. This is accessed from 'ADMIN' within the top navigation bar.
• Administrative tasks include:
  • Registration of new users
  • Project settings
  • Management of project members
  • Management of source code repositories
  • WebDAV access
  • Management of mailing lists for communication with project owners (despots), all community members of MuleForge and user support.

Atlassian JIRA Issue Tracker

• Each project has its issues. JIRA helps to keep track of them as they are shared between the MuleForge community members. JIRA is used to:
  • Report bugs
  • Request/suggest new features
  • Request/suggest an improvement
• Read the Atlassian's JIRA users' guide for information about how to use JIRA.

Atlassian Confluence

• Confluence is used to provide wiki space for MuleForge itself and for each MuleForge project.
• Each MuleForge project is provided a homepage which can be edited by members of the project in order to write project documentation, project examples, installation instructions, users' guide and any other relevant information deemed necessary by the members of the project.
• To go to the wiki space of a particular project, click the homepage link of that project.
• Read the Atlassian's CONFLUENCE users' guide for information about how to use Confluence.

Atlassian Bamboo

• Bamboo is a continuous integration (CI) server.
• It is used to:
  • Build source code
  • Deploy snapshots
  • Provide notifications for a build failure and the first successful build thereafter.
  • Identify patterns and linkages across builds.
• Read the Atlassian's BAMBOO guide for information about how to use Bamboo.

Atlassian Fisheye

• Fisheye is a source code monitoring tool.
• It is mainly used to track changes made to a project's source code.

Subversion (SVN)

• SVN is the version control system used by MuleForge projects.
• Read the following users' guide sections:
• Browse Source Code (checking out source code for read-only access)
• Access A Project's Source Code (checking out source code for read-write access)

Maven

• Maven is the software project management tool used by MuleForge projects.
• It is the standard build tool. Currently, Maven2 (M2) version 2.0.7 is being used to build new projects.

Jive Forums

• A forum is created for each project.
• The forums are organised according to the project category, namely transport projects; module projects; example projects and tools projects.
• There is also another forum for discussing project proposals.