Difference between revisions of "Contributing code"

From Omni
Jump to: navigation, search
(Steps to Contribute Code to Omnirom)
Line 2: Line 2:
 
== Steps to Contribute Code to Omnirom ==
 
== Steps to Contribute Code to Omnirom ==
  
 +
The beauty of open source projects is the ability for even the most novice of developers to be involved in determining the trajectory of the project. The difficulty is in knowing exactly how to submit your patch for code review and (hopefully) inclusion into the project.
 +
 +
Below are the simple, basic steps for contributing code:
 +
# Begin by performing a ''repo sync'' so that we know we’re dealing with the most recent versions of the code. We're also assuming that you have your Omnirom repo in ~/android/omni:
 +
  cd ~/android/omni
 +
  repo sync
  
 
== Licensing ==
 
== Licensing ==
  
 
It is important that any code you contribute follows either the existing licensing, or utilizes the correct licensing. For pre-created headers, see the [[License template]]
 
It is important that any code you contribute follows either the existing licensing, or utilizes the correct licensing. For pre-created headers, see the [[License template]]

Revision as of 19:03, 1 November 2013

Steps to Contribute Code to Omnirom

The beauty of open source projects is the ability for even the most novice of developers to be involved in determining the trajectory of the project. The difficulty is in knowing exactly how to submit your patch for code review and (hopefully) inclusion into the project.

Below are the simple, basic steps for contributing code:

  1. Begin by performing a repo sync so that we know we’re dealing with the most recent versions of the code. We're also assuming that you have your Omnirom repo in ~/android/omni:
 cd ~/android/omni
 repo sync

Licensing

It is important that any code you contribute follows either the existing licensing, or utilizes the correct licensing. For pre-created headers, see the License template