1
edit
Changes
→Project Plan
== Project Plan ==
Tracking mechanism (bugzilla, trac, : github, ...):
Key contacts:
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.1 Proof of concept - Research into kernel and obtain the file that is used as the Raspberry Pi Kernel utility that creates . Successfully Package the special header for bootloader, locate and obtain sourcefile using rpmbuild into an SRPM & RPM * 0.2 Initial working state - Create Test the RPM for errors with rpmlint, mock, koji. Attempt to have errors resolved and build RPM then have package from reviewed by the source obtained, check for errorscommunity* 0.3 Completed working state - Continue testing of the Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package for final release.
== Communication ==