1
edit
Changes
→Blogs
= Project Name Package the Raspberry Pi Kernel Utility =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
<!-- 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. -->
Nam Nguyen
== Project Contributor(s) ==
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. -->
== Project Details Kernel Utility Package Releases ==[http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release01/ Release 0.1]
[http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release02/ Release 0.2]
[http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release03/update/ Release 0.3]
[http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release03/update/raspi-tools.spec SPEC File]
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->
== Project Plan ==
Tracking mechanism (bugzilla, trac, : github, ...):
Key contacts:ctyler
<!-- Add links to any mentors or key participants in the community. -->
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. -->
* 0.1Proof 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.2Initial 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.3Completed working state - Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package.
== Communication ==
=== Upsteam Wiki and Web ===
[http://www.github.com/raspberrypi/tools/tree/master/mkimage https://github.com/raspberrypi/tools/tree/master/mkimage]
<!-- Links to upstream wiki/web pages -->
=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
[http://sharethecode.blogspot.ca// http://sharethecode.blogspot.ca/]
==== Seneca Particpants ====
Joseph Nam Nguyen
==== Non-Seneca Participants ====
==== Planets ====
[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]
<!-- Links to any planets related to this project -->
