Difference between revisions of "Create the Raspi Repositories"
(→Project Plan) |
(→Project Plan) |
||
| Line 38: | Line 38: | ||
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
* 0.1 Release - proof of concept: Prepare keys for the F17 Raspberry Pi remix files, test sign packages, test and develope a basic SOP concept/outline. | * 0.1 Release - proof of concept: Prepare keys for the F17 Raspberry Pi remix files, test sign packages, test and develope a basic SOP concept/outline. | ||
| − | * 0.2 Refine Standard Signing Procedure, create repos for a pre-release package, test pre-release for bugs. | + | * 0.2 Release - Refine Standard Signing Procedure, create repos for a pre-release package, test pre-release for bugs. |
| − | * 0.3 Release | + | * 0.3 Release - Complete package containing public keys and repo files. |
== Communication == | == Communication == | ||
Revision as of 20:24, 8 February 2012
Contents
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 Release - proof of concept: Prepare keys for the F17 Raspberry Pi remix files, test sign packages, test and develope a basic SOP concept/outline.
- 0.2 Release - Refine Standard Signing Procedure, create repos for a pre-release package, test pre-release for bugs.
- 0.3 Release - Complete package containing public keys and repo files.
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
http://sbr600blog.blogspot.com/
Seneca Particpants
Andrew Greene
