Changes

Jump to: navigation, search

Sample Project

21 bytes added, 20:04, 20 October 2013
no edit summary
= Project Name =Profile and Improve RPM and YUM performance on the Pi
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
<!-- Description should be no longer than a paragraph. Include links Profiling the YUM and RPM performance to any relevant on-line resourcesidentify which parts of the processes are taking time. For exampleAfter identifying, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]improve the performance. -->
== Project Leader ==
<!-- Name(s) of primary person working on the project. If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing what. For example: Include links to personal pages within wiki and to blog sites. -->Jose Giagonia
== Project Contributor(s) ==
== Project Plan ==
 
Identify the tools fro profiling.
Initial testing phase of YUM and RPM without profiling.
Identify The processes which takes time.
Improve the processes.
Test again and take note of the results.
=== Tracking ===
Goals for each release and plans for reaching those goals:
<!-- Note: Each student must 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.1Identify which part of YUM and RPM spends alot of time.* 0.2An improvement in performance.* 0.3A package that is improved for Pi.
== Communication ==

Navigation menu