Skip to main content
Jump to: navigation, search

Orion/Contributing Code

< Orion
Revision as of 17:38, 11 January 2012 by Grant (Talk | contribs) (initial)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Orion project welcomes code contributions from the public. This page details setting up a work environment and submitting code changes for review and inclusion by a committer.

Identifying an opportunity

Bug fixes are the most common type of code contribution. For a list of currently-open Orion bugs see the Eclipse Bugzilla database. If a bug's Assignee is an "inbox" name (eg.- "") then it has not been assigned to anyone yet, and is a good candidate for investigation. If you observe a bug in Orion that does not already have a bug report for it then be sure to first log a report, and in the initial comment specify that you are investigating a fix for it. The report should be logged up-front so that if the bug is not one that should be fixed (eg.- it is actually working as designed, its component is in the midst of a re-write, etc.), then a committer can add a follow-up comment indicating that the bug is not worth investigating.

New features/enhancements can also be contributed, but for these it is important that a committer comment in its bug report indicate that the feature is desirable. The potential for feature work in any project is limitless, but not all features are good fits, so a feature that was not pre-approved by a committer risks not being ultimately accepted.

Set up a Git repository

The first step is to establish a Git repository. The remainder of this page assumes that GitHub is being used to host your repository, since it is a well-established Git hosting service and the Orion repository is mirrored there. However using GitHub is not a strict requirement.

Once you have a user account on GitHub, start by creating forks of the and/or repositories. These repositories will contain the latest Orion code in their "master" branch, and will eventually receive your code changes for submission.

Clone your repository

The next step is to clone your newly-created repository into your Orion environment, which is described in detail here. Once this is complete the orion.client and/or orion.server projects will be created in your Orion workspace, and are ready for hacking.

Commit your changes

Once your changes are ready for submission, you first commit them to the Git repository in your Orion environment, and then push this repository to your Git repository on GitHub. For more detailed information on using Orion's Git facilities see the Orion User Guide.

Request adoption of your changes

Finally, on GitHub create a Pull Request for your changes, which creates a page similar to Paste this Pull Request link into a comment in the Orion bug report and add "patch" to its Keyword field. It will then be up to a committer to review your change, ask questions, suggest improvements, etc. Once the change is deemed to be ready then the committer can add it to the Orion repository.

Back to the top