Project Menu

Support Project

TestPage

Contributing to the omapandroid project uses the same process defined by the OHA for contributing to the Android project. However, omapandroid introduces a second review site to handle changes specific to OMAP.

Click on the settings menu in the top right corner. Then select the "Contact Information" tab. Make sure you fill out the name and email fields and save it.

Click on the "SSH Keys" tab. Upload your ssh public key. Not sure how - click on the "Guide to SSH Key's" link and follow the instructions for your OS.

Remember - you need to save your ssh key for both review.source.android.com and review.omapzoom.org

SSH Proxy Setup

The repo tool uses ssh to access Gerrit. If you are not behind a firewall, then if the keys are correct, everything should be fine. However, if you are behind a firewall, you will need to tell ssh about it. If you haven't already install corkscrew for using git behind a firewall, do so now. See this link for more info. Then add the following to your ~/.ssh/config file and substitue your path to corkscrew where it says "<path to corkscrew>" and your web proxy server where it says "<proxy name>".

Testing the Connection

Try to ssh to Gerrit - it should respond with "gerrit: no shell available". Log into your account on Gerrit and click on the "Settings" menu. Note the name is states as SSH Username. Now issue the following command from the machine(s) you plan on using for 'repo upload'.

ssh -p 29418 <ssh username>@review.omapzoom.org

If it comes back with "gerrit: not shell available" you are good to go.

Uploading Changes

Do the normal "repo init" and "repo sync" to get the current to work with. The next step is critical - you must have started a working branch to do an upload. It is important to note that all changes done on a given branch are grouped and dependent on each other. If you mix several different unrealated develpoment tasks on the same branch, you run the risk of creating unwanted depencies that could hold up unrelated patches later. Always start separate branches for each of your development activities.

Once you have a branch started. Edit files as Normal and commit them to your local git trees as you need. When you are ready to push the patch up, do a 'repo upload'. If all is well, you will see your patch posted on the gerrit review sites.