CodeAurora Project Setup

Last modified by Lisa Lammens on 2017/07/07 18:51

Please copy/paste and fill out this form.  Email completed form to: ITPeople AT codeaurora DOT org

Here is what ITPeople will need to create a new CAF project:

  • Name of Project (please choose a name that can not be confused with similar projects from other CAF members. i.e. "Linux BSP" is unacceptable, "MyProduct Open Embedded BSP for SomeSoC" is fine)
  • Short Description of Project (1-2 sentences)
  • Long Description of Project (what is it, what does it do, etc. so the open source community can understand it and use it)
  • Open Source Licenses used in Project (BSD?, Apache?, GPL? -- only OSI approved licenses may be used)
  • Project Admin name/email contact (someone who will be responsible for this project)
  • Secondary Project Admin name/email contact (someone who will be backup for this project)

Here is a CAF wiki template for all the CAF projects. It is the responsibility of the Project Admin to customize the wiki page for your project. Do not leave the template wiki as your project wiki page. 

Register for a CodeAurora Forum account

Give us your SSH key

  • Please provide contributors SSH keys via PGP/GPG (NOT plain text via email; if emailed plain text, that SSH key will be blacklisted).  See "Submitting your SSH key to CAF".

Code repos section

  • each new repo request should have a repo description included that will be displayed in cgit.  For large amounts of repos, this list should be included as a CSV file:

     repo path, repo description

  • is this a fork of an existing project?
  • are there any CAF projects that need to be pulled in? (is this a one time or continual? if continual, how often?)
  • are there any other outside (non-CAF) projects that need to be pulled in? (is this a one time or continual? if continual, how often?)
  • are there any added repos need to be created (new work)?
  • who will need access? (please provide contributors SSH keys via PGP/GPG (NOT plain text via email; if emailed plain text, that SSH key will be blacklisted).  See "Submitting your SSH key to CAF".

Patches section (tarballs are not patches)

  • will you require the ability to upload patches?
  • what is the title of the patches area?
  • what is the description of the patches?

Mirrored source

  • do you need to mirror any source tarballs?
  • provide list of tarballs need mirrored
  • need to know: source url, md5 sum, license, (bitbake file/ebuild/debian source file/rpm source file, etc) or why you need this mirrored?

Pushing code section

  • will you require the ability to push code to other repos?
  • do you have write access permission from the project admins?

Misc section

  Please describe any other configurations needed for your project

    

Tags:
Created by Greg Stinocher on 2013/03/14 09:43
   
This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 7.4.3 - Documentation