Difference between revisions of "Package the Raspberry Pi kernel utility"

From CDOT Wiki
Jump to: navigation, search
(Project Name)
(Project Plan)
Line 29: Line 29:
 
== Project Plan ==
 
== Project Plan ==
  
Tracking mechanism (bugzilla, trac, github, ...):
+
Tracking mechanism : github
  
 
Key contacts:
 
Key contacts:
Line 36: Line 36:
 
Goals for each release and plans for reaching those goals:
 
Goals for each release and plans for reaching those goals:
 
<!-- 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 Proof of concept - Research into kernel utility that creates the special header for bootloader, locate and obtain source
+
* 0.1 Proof of concept - Research and obtain the file that is used as the Raspberry Pi Kernel utility. Successfully Package the file using rpmbuild into an SRPM & RPM 
* 0.2 Initial working state - Create and build RPM package from the source obtained, check for errors
+
* 0.2 Initial working state - Test the RPM for errors with rpmlint, mock, koji. Attempt to have errors resolved and then have package reviewed by the community
* 0.3 Completed working state - Continue testing of the package for final release
+
* 0.3 Completed working state - Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package.
  
 
== Communication ==
 
== Communication ==

Revision as of 02:38, 8 March 2012

Package the Raspberry Pi Kernel Utility

Project Description

The Raspi bootloader requires a special header at the start of the kernel file in order to correctly load it into memory. The tool which creates this header needs to be packaged in Fedora.

Expected outcome: a Fedora package for the Raspberry Pi kernel utility.

Skills required: packaging

Project Leader(s)

Nam Nguyen

Project Contributor(s)

Project Details

Project Plan

Tracking mechanism : github

Key contacts:

Goals for each release and plans for reaching those goals:

  • 0.1 Proof of concept - Research and obtain the file that is used as the Raspberry Pi Kernel utility. Successfully Package the file using rpmbuild into an SRPM & RPM
  • 0.2 Initial working state - Test the RPM for errors with rpmlint, mock, koji. Attempt to have errors resolved and then have package reviewed by the community
  • 0.3 Completed working state - Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package.

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Seneca Particpants

Nam Nguyen

Non-Seneca Participants

Planets

Project News