Difference between revisions of "Sample Project"

From CDOT Wiki
Jump to: navigation, search
(Undo revision 101129 by Jose Francisco Gonzales Giagonia (Talk))
Line 1: Line 1:
= Project Name = Profile and Improve RPM and YUM performance on the Pi
+
= Project Name =
 
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
  
 
== Project Description ==
 
== Project Description ==
  
Profiling the YUM and RPM performance to identify which parts of the processes are taking time. After identifying, improve the performance.
+
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
  
 
== Project Leader ==
 
== Project Leader ==
  
Jose Giagonia
+
<!-- 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. -->
  
 
== Project Contributor(s) ==
 
== Project Contributor(s) ==
Line 21: Line 25:
  
 
== Project Plan ==
 
== 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 ===
 
=== Tracking ===
Line 38: Line 36:
 
Goals for each release and plans for reaching those goals:
 
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. -->
 
<!-- 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.1 Identify which part of YUM and RPM spends alot of time.
+
* 0.1
* 0.2 An improvement in performance.
+
* 0.2
* 0.3 A package that is improved for Pi.
+
* 0.3
  
 
== Communication ==
 
== Communication ==

Revision as of 20:05, 20 October 2013

Project Name

Project Description

Project Leader

Project Contributor(s)

Project Details

Project Plan

Tracking

Key contacts

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1
  • 0.2
  • 0.3

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News