Open source license process

1) Make sure that you have full and exclusive rights to the IP that you're trying to license.
     For instance, all employees that contributed to the code should be under contract that they don't own anything that they create while they are employed.
2) Choose what license to use
     Use these as guides and reference: http://choosealicense.com/ and http://oss-watch.ac.uk/resources/licdiff
3) Make sure to license non-software items e.g. images, sounds, documentation or databases (if there's any)
     Open source licenses are designed to be used on software codes only.
     http://creativecommons.org/ -- for images, sounds and documentation
     http://opendatacommons.org/licenses/ -- for databases
4) Read the Open Source Definition and ensure that your license complies with it Check it here http://opensource.org/docs/osd
5) Identify the type of submission (Retirement, Legacy Approval or Approval)
6) Ensure you have appropriate standing to submit such a request
7) Subscribe to license-review (if you aren't already)
8) Submit a formal request to license-review. For new licenses, this should happen before they are finalized to allow for any necessary changes
9) The request email must include: A) the submission type and license name in subject field (to ensure proper tracking) B) a plaintext copy of the license C) the supporting data listed http://pastebin.com/raw.php?i=Pk9psUiB (as appropriate for the type of submission) D) a link to earlier public discussions (if any)

Note: Processing for review takes about 30 business days

Once approved, take note when applying the license: (at minimum you should do this)
1) State on your website which licence is applied (preferably on your home page and your downloads page)
2) Provide the full text of the licence on your website
3) Provide the full text of the licence in the root directory of your source project (usually in a file called LICENSE.TXT)
4) Provide a boilerplate notice in the head of each file in the source distribution (The boilerplate text used varies from licence to licence. You will usually find further discussion on how to apply a licence documented alongside the licence in its original home.)
5) Provide the full text of the licence in the root directory of your non-source project distributions (usually in a file called LICENSE.TXT).