Difference between revisions of "Create the Raspi Repositories"

From CDOT Wiki
Jump to: navigation, search
(Blogs)
(Project Name)
Line 1: Line 1:
 
= Project Name =
 
= Project Name =
 
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 +
Raspi Repositories
  
 
== Project Description ==
 
== Project Description ==
  
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 +
Set up the repositories to distribute the F17 Raspberry Pi remix files, including:
  
 +
Setting up the signing keys
 +
Creating a standard signing procedure (SOP) for signing
 +
Creating a 'release' package containing the public keys and repo files
 +
 +
Expected outcome: repos, release package, SOP
 
== Project Leader(s) ==
 
== Project Leader(s) ==
  
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
 +
Andrew Greene
  
 
== Project Contributor(s) ==
 
== Project Contributor(s) ==

Revision as of 20:37, 8 February 2012

Project Name

Raspi Repositories

Project Description

Set up the repositories to distribute the F17 Raspberry Pi remix files, including:

Setting up the signing keys Creating a standard signing procedure (SOP) for signing Creating a 'release' package containing the public keys and repo files

Expected outcome: repos, release package, SOP

Project Leader(s)

Andrew Greene

Project Contributor(s)

Project Details

Project Plan

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:

Goals for each release and plans for reaching those goals:

  • 0.1
  • 0.2
  • 0.3

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

http://sbr600blog.blogspot.com/

Seneca Particpants

Andrew Greene

Non-Seneca Participants

Planets

Project News