Changes

Jump to: navigation, search

SBR600 Potential Projects

5,663 bytes removed, 01:11, 7 February 2012
Reverted edits
Maximum number of participants: 1
 
 
= Project Name =
<!-- 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 to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
== Project Leader(s) ==
 
<!-- 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. -->
 
== Project Contributor(s) ==
 
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
 
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. -->
 
== Project Details ==
 
<!-- 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:
<!-- 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.1
* 0.2
* 0.3
 
== Communication ==
 
=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
 
=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->
 
=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
 
=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
 
=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
==== Seneca Particpants ====
 
==== Non-Seneca Participants ====
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
==== Planets ====
<!-- Links to any planets related to this project -->
 
== Project News ==
 
<!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->
== Generate an RPM-based Raspberry Pi kernel ==
Note: the liveusb-creator tool goes through a number of setup steps that are not required for an SD card. On the other hand, creating an SD card involves a few steps that are not necessary for a live USB. Therefore it might be appropriate to create a separate tool rather than modifying the liveusb-creator tool. Also, there are other efforts taking place within the Raspberry Pi community which might do the same thing; if one of those efforts reaches a stable release, it might be possible to package that for Fedora.
'''Note:'''Maximum number of participants: 3 = Project Name =<!Jon Chiappetta has started work on a similar tool -- Replace "Project Name" with the actual name of the participants in this project in the line above. --> == Project Description == <!-- Description should be no longer than a paragraph. Include links to any relevant onco-line resources. For example, [http:ordinate//fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. --> == Project Leader(s) == <!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss work with other leaders first. Include links to personal pages within wiki and to blog sites. --> == Project Contributor(s) == <!-- Name(s) of people casually working Jon on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them. NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. --> == Project Details == <!-- 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 tool (bugzilla, trac, github, ...fossjon in #seneca): Key contacts:<!-- 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.1* 0.2* 0.3 == Communication == === Mailing Lists ===<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> === Upsteam Wiki and Web ===<!-- Links to upstream wiki/web pages --> === Links/Bugs/Tracking ===<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> === Source Code Control ===<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories --> === Blogs ===<!-- Links to the blogs of people involved, both inside and outside Seneca --> ==== Seneca Particpants ==== ==== Non-Seneca Participants ====<!-- Links to the blogs of any non-Seneca participants in this project -->
==== Planets ====<!-- Links Expected outcome: a Fedora package of a tool to any planets related to this project -->install the Raspi distribution image on an SD card. Ideally, a Windows version as well.
== Project News ==Skills required: scripting (python), system administration, testing/QA
<!-- This is where a permanent record Maximum number of your releases participants: 3 (scripting, Fedora packaging and updates will go. In these you should discuss the status or your worktesting, your interactions with other members of the community (e.g., Seneca Windows packaging and Mozillatesting), problems you have encountered, etc. -->
== Create the F17 Raspberry Pi image ==
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/wiki/Special:MobileDiff/80777"

Navigation menu