Child pages
  • Contribution Process
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Note

This contribution process is in the process of being replaced and should be used strictly on an interim basis. Please see:

http://strictlygeeking.blogspot.com/2012/03/new-development-and-contribution-model.html

With oi-build, we have tried to make the contribution process as simple as possible. To do this, we leverage the free public Mercurial hosting service, BitBucket.

The process consists of:

  1. First, create a bug or feature on the issue tracker describing what you want to achieve. If it's an existing component, please show consideration to anyone who's previously updated the component (check hg log for all source) by subscribing them to the issue.
  2. Sign up to BitBucket
  3. Fork oi-build within BitBucket so you have your own copy to push to
  4. Clone oi-build either from BitBucket or hg.openindiana.org locally in your development environment
  5. Make your changes, then hg commit, using the issue number and description as the commit message.
  6. Push to BitBucket
  7. Email BitBucket "Compare Fork" URL to oi-dev asking for a review or an RTI (request to integrate)

A member of the OI commit team will review your changeset. If we feel it needs work, we'll provide assistance. When it's ready to be integrated, we'll pull it into oi-build.

Guidelines

The issue number in 1 above serves as a way of tracking commits easily. When mailing oi-dev with a request for a code review, please use the subject "1234 issue-subject", eg "1273 Update rdesktop to 1.7.0".

When committing with mercurial, you MUST commit using this format. Please see our commit history to see how this looks in reality.

  • No labels