Difference between revisions of "Features/SoaS Remixability"

Revision as of 06:24, 27 July 2010

Summary

Build Your Own Soas Remix and Share your Custom.ks File on the wiki.

Owner

This should link to your home wiki page so we know who you are

Name: [| Thomas Gilliard]

Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved

Email: satellit@bendbroadband.com

Current status

Targeted release: (Soas v4)
Last updated: (07/27/2010)
Percentage of completion: 99%

Detailed Description

Simplified instructions on how to compose or edit a kickstart file for Soas, how to install livecd-tools and spin-kickstarts, and how to enter the commands to create a custom remix.
Request for feedback and e-mail with attachment of their working .ks file which we will post on the wiki. This will allow others to study and learn how to do it:
we plan to have a listing of Customized kickstart.files to share on the WIKI

We will list them here so others can try them out and learn from them.

Please send e-mail to:

To: soas@lists.sugarlabs.org
Subject: [Custom KS]-{Name of your kickstart file}
*Attach your Custom.ks file*
PLEASE INCLUDE THE FOLLOWING INFORMATION in e-mail:
Sugar Version                    :                  
(0.82; 0.86.x; 0.88.x; 0.89.x)
Country / Deployment             :                      
Build system fedora version      :                    
Number of USB's in Deployment    :  
PC/Netbooks used                 :             
Notes and Any Bug No's submitted :

Benefit to Sugar

What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?

Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.

Scope

It works now. Instructions are written and method is tested

http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table#Test_results

All a User has to do to implement this is to install livecd-tools and spin-kickstarts in their version of fedora:

su -c 'yum install livecd-tools spin-kickstarts'

And follow instructions.

UI Design

Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.

How To Test

Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29

Follow these instructions and burn resulting .iso to CD ant test it by Booting it.

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.

Dependencies

None that I know of.

Contingency Plan

If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.

Documentation

http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29

Release Notes

The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.

Comments and Discussion

See discussion tab for this feature

@@ Line 6: / Line 6: @@
 </noinclude>
-'''Comments and Explanations:'''
-There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
 <!-- All fields on this form are required to be accepted.
@@ Line 14: / Line 11: @@
 <!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
 == Summary ==
 Build Your Own Soas Remix and Share your Custom.ks File on the wiki.
@@ Line 31: / Line 27: @@
 == Detailed Description ==
+*Simplified instructions on how to compose or edit a kickstart file for Soas, how to install livecd-tools and spin-kickstarts, and how to enter the commands to create a custom remix.
+*Request for feedback and e-mail with attachment of their working .ks file which we will post on the wiki. This will allow others to study and learn how to do it:
+* we plan to have a listing of Customized kickstart.files to share on the WIKI
+: We will list them here so others can try them out and learn from them.
+::Please send e-mail to:
+ To: soas@lists.sugarlabs.org
+ Subject: [Custom KS]-{Name of your kickstart file}
+ *Attach your Custom.ks file*
+ PLEASE INCLUDE THE FOLLOWING INFORMATION in e-mail:'''
+ Sugar Version                    :
+ ''(0.82; 0.86.x; 0.88.x; 0.89.x)''
+ Country / Deployment             :
+ Build system fedora version      :
+ Number of USB's in Deployment    :
+ PC/Netbooks used                 :
+ Notes and Any Bug No's submitted :
 == Benefit to Sugar ==