Difference between revisions of "Create the F17 Raspberry Pi image"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= Create the F17 Raspberry Pi image = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == Based on feedback on the …')
 
 
(18 intermediate revisions by 2 users not shown)
Line 15: Line 15:
 
== Project Leader(s) ==
 
== Project Leader(s) ==
  
 +
[http://zenit.senecac.on.ca/wiki/index.php/User:Jfulton Jesse Fulton]
 
<!-- 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. -->
 
<!-- 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) ==
 
== Project Contributor(s) ==
  
 +
M.A Sajed Shadani
 
<!-- 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.
 
<!-- 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.
  
Line 35: Line 37:
 
Goals for each release and plans for reaching those goals:
 
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. -->
 
<!-- 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  Research and get familiar with the Raspberry Pi project.  Research and identify issues with the previous script for the F14 Raspberry Pi image.  
+
* 0.1  Research and get familiar with the Raspberry Pi project.  Research and acquire a mkrootfs script.
* 0.2  Create the script that addresses the previous issues that can be used in the F17 alpha/beta image for Raspberry Pi
+
* 0.2  Edit the script that will addresses the previous issues that can be used in the F17 alpha/beta image for Raspberry Pi
 
* 0.3  Test and complete a error free script that will be able to be implemented in the final distribution of a F17 image for the Raspberry Pi
 
* 0.3  Test and complete a error free script that will be able to be implemented in the final distribution of a F17 image for the Raspberry Pi
  
Line 46: Line 48:
 
** [https://admin.fedoraproject.org/mailman/listinfo/secondary secondary] - For discussion of secondary architectures
 
** [https://admin.fedoraproject.org/mailman/listinfo/secondary secondary] - For discussion of secondary architectures
 
** [https://admin.fedoraproject.org/mailman/listinfo/arm arm] - For discussion of the ARM secondary architecture
 
** [https://admin.fedoraproject.org/mailman/listinfo/arm arm] - For discussion of the ARM secondary architecture
 
 
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
 
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
  
Line 57: Line 58:
  
 
*  [http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/x86_64/iso/ Download F17 Alpha]
 
*  [http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/x86_64/iso/ Download F17 Alpha]
 +
 +
*  [http://paulfedora.wordpress.com/2010/12/15/fedora-13-arm-alpha-root-file-system/ Paul Whalen's Blog on mkrootfs for F13]
 
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
 
<!-- 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 ===
 
=== Blogs ===
 +
[http://jessefulton.wordpress.com/ http://jessefulton.wordpress.com/]<p>
 +
[http://sajed481.wordpress.com/ http://sajed481.wordpress.com/]
 
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
  
 
==== Seneca Particpants ====
 
==== Seneca Particpants ====
  
Jesse Fulton and M.A Sajed Shadani
+
[http://zenit.senecac.on.ca/wiki/index.php/User:Jfulton Jesse Fulton] and M.A Sajed Shadani
  
 
==== Non-Seneca Participants ====
 
==== Non-Seneca Participants ====
Line 76: Line 78:
  
 
== Project News ==
 
== Project News ==
 +
 +
0.1 & 0.2 Released!  Go to my blog to find out more --> [http://jessefulton.wordpress.com/2012/04/05/raspberry-pi-f17-image-creation/ 0.1/0.2-BLOG]
 +
 +
-------------
 +
 +
0.3 Released!  Go to my blog to see more --> [http://jessefulton.wordpress.com/2012/04/12/0-3-release-raspberry-pi-f17-image-creation/ 0.3-BLOG]
 +
 +
  
 
<!-- 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. -->
 
<!-- 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. -->

Latest revision as of 03:42, 12 April 2012

Create the F17 Raspberry Pi image

Project Description

Based on feedback on the F14 Raspberry Pi image, create an F17 alpha/beta image for the Raspberry Pi.

This will involve modifying (or creating) a script to produce the Raspi rootfs, putting the rootfs and image into the final format for distribution.

Note: the final version of F17 won't be ready until just after this course ends. The image will need to be based on the F17 alpha/beta package set.

Expected outcome: a F17 image creation script.

Project Leader(s)

Jesse Fulton

Project Contributor(s)

M.A Sajed Shadani

Project Details

Project Plan

Key contacts:


Goals for each release and plans for reaching those goals:

  • 0.1 Research and get familiar with the Raspberry Pi project. Research and acquire a mkrootfs script.
  • 0.2 Edit the script that will addresses the previous issues that can be used in the F17 alpha/beta image for Raspberry Pi
  • 0.3 Test and complete a error free script that will be able to be implemented in the final distribution of a F17 image for the Raspberry Pi

Communication

Mailing Lists

  • Fedora Mailing Lists
    • secondary - For discussion of secondary architectures
    • arm - For discussion of the ARM secondary architecture

Upsteam Wiki and Web

Links/Bugs/Tracking

Blogs

http://jessefulton.wordpress.com/

http://sajed481.wordpress.com/

Seneca Particpants

Jesse Fulton and M.A Sajed Shadani

Non-Seneca Participants

Planets

Project News

0.1 & 0.2 Released! Go to my blog to find out more --> 0.1/0.2-BLOG


0.3 Released! Go to my blog to see more --> 0.3-BLOG