Difference between revisions of "Firstboot Module"
(→Project Name) |
(→Project Plan) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
<!-- 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. --> | ||
| − | Firstboot | + | Firstboot Module |
== Project Description == | == 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]. --> | <!-- 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]. --> | ||
| + | |||
| + | Firstboot is the program that runs on the first boot of a Fedora or Red Hat Enterprise Linux system that allows you to configure more things than the installer allows. | ||
| + | The firstboot package asks the user specific questions when the system starts for the first time. Since Raspberry Pi systems are installed by copying the SD card, additional questions should be asked during the first boot -- for example, the root password and timezone should be set. This project involves writing and packaging additional modules for firstboot for use with the Raspi (and potentially other ARM systems). | ||
| + | |||
| + | Expected outcome: changes for firstboot committed upstream, or a package that extends firstboot packaged in Fedora. | ||
== Project Leader(s) == | == Project Leader(s) == | ||
| Line 31: | Line 36: | ||
<!-- Add links to any mentors or key participants in the community. --> | <!-- Add links to any mentors or key participants in the community. --> | ||
Chris Tyler and Chris Lumens | Chris Tyler and Chris Lumens | ||
| + | |||
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 Split work evenly between each other and learn to write with Python. Look at anaconda and examine its python script. | + | * 0.1 Split work evenly between each other and learn to write with Python. Look at anaconda and examine its python script. Plan to release a test script. |
| − | * 0.2 | + | * 0.2 Start having scripts ready and package to see if it performs its function. Plan to release test results. |
| − | * 0.3 | + | * 0.3 Test package and see if it's usable. Plan to release package. |
== Communication == | == Communication == | ||
| Line 66: | Line 72: | ||
==== Non-Seneca Participants ==== | ==== Non-Seneca Participants ==== | ||
<!-- Links to the blogs of any non-Seneca participants in this project --> | <!-- Links to the blogs of any non-Seneca participants in this project --> | ||
| − | Planning to speak with Chris Lumens (clumens on IRC, <clumens@redhat.com>) was one of the main developers.(Suggestion by Chris Tyler to contact him.) | + | Planning to speak with Chris Lumens (clumens on IRC, <clumens@redhat.com>) who was one of the main developers.(Suggestion by Chris Tyler to contact him.) |
| + | |||
==== Planets ==== | ==== Planets ==== | ||
<!-- Links to any planets related to this project --> | <!-- Links to any planets related to this project --> | ||
Latest revision as of 22:27, 8 February 2012
Contents
Project Name
Firstboot Module
Project Description
Firstboot is the program that runs on the first boot of a Fedora or Red Hat Enterprise Linux system that allows you to configure more things than the installer allows. The firstboot package asks the user specific questions when the system starts for the first time. Since Raspberry Pi systems are installed by copying the SD card, additional questions should be asked during the first boot -- for example, the root password and timezone should be set. This project involves writing and packaging additional modules for firstboot for use with the Raspi (and potentially other ARM systems).
Expected outcome: changes for firstboot committed upstream, or a package that extends firstboot packaged in Fedora.
Project Leader(s)
Craig and Celeste
Project Contributor(s)
Project Details
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts: Chris Tyler and Chris Lumens
Goals for each release and plans for reaching those goals:
- 0.1 Split work evenly between each other and learn to write with Python. Look at anaconda and examine its python script. Plan to release a test script.
- 0.2 Start having scripts ready and package to see if it performs its function. Plan to release test results.
- 0.3 Test package and see if it's usable. Plan to release package.
Communication
Mailing Lists
announce@lists.fedoraproject.org
arm@lists.fedoraproject.org
devel@lists.fedoraproject.org
secondary@lists.fedoraproject.org
Upsteam Wiki and Web
Links/Bugs/Tracking
http://fedoraproject.org/wiki/FirstBoot
http://fedoraproject.org/wiki/FirstBoot/Modules
Source Code Control
Blogs
http://challahar.wordpress.com/
Seneca Particpants
Non-Seneca Participants
Planning to speak with Chris Lumens (clumens on IRC, <clumens@redhat.com>) who was one of the main developers.(Suggestion by Chris Tyler to contact him.)
