Difference between revisions of "Features/SoaS Remixability"

From Sugar Labs
Jump to navigation Jump to search
m (FGrose moved page Features/Soas V4/Remixability to Features/SoaS Remixability: simplify name)
 
(29 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
<noinclude>{{TOCright}}
+
<noinclude>[[Category:Feature Page Incomplete]]
−
[[Category:Feature Page Incomplete]]
+
[[Category:Feature|SoaS Remixability]]
−
[[Category:Feature|<Remixability>]]
 
−
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
 
−
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
 
</noinclude>
 
</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.
 
<!-- All fields on this form are required to be accepted.
Line 14: Line 8:
  
 
<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
 
<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
 +
== Summary ==
  
−
== Summary ==
+
The official SoaS image that is released can be used as a base to re-spin custom (unofficial and unsupported) SoaS remixes using the instructions on our official [[Sugar_on_a_Stick/Documentation_SOP|Customization Guide]] and a few additional FOSS tools outlined in the Guide.
−
Build Your Own Soas Remix and Share your Custom.ks File on the wiki.
+
 
 +
This feature proposes:
 +
 
 +
* The development of a page on the SL wiki for highlighting classroom-made remixes, their kickstart files, and details on their usage
 +
* The creation of 2-4 sample remixes for specific types of classrooms to pre-populate that wiki page
 +
* An experimental remix image-building service available for the first 2 months after the Mango Lassi release
 +
* Edits to the Customization Guide version for Mango Lassi that reflect these changes
  
 
== Owner ==
 
== Owner ==
−
''This should link to your home wiki page so we know who you are''
 
−
* Name: [[http://wiki.sugarlabs.org/go/User:Satellit| 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''
+
* Name: [[User:Satellit | Thomas Gilliard]]
−
* Email: satellit@bendbroadband.com
+
 
 +
* Email: satellit <at> bendbroadband <dot> com
  
 
== Current status ==
 
== Current status ==
−
* Targeted release: (Soas v4)
+
* Targeted release: (Soas v4 [[Sugar on a Stick/Mango Lassi]])
−
* Last updated: (07/27/2010)
+
* Last updated: [[User:Mchua|Mchua]] 23:01, 2 August 2010 (EDT)
−
* Percentage of completion: 99%
+
* Percentage of completion: 70%
  
 
== Detailed Description ==
 
== Detailed Description ==
 +
 +
=== Wiki page ===
 +
 +
The creation of a page that:
 +
 +
* Describes remixes
 +
* Makes it clear that remixes are unsupported
 +
* Links to the Customization Guide as the canonical resource on how to make remixes
 +
* Lists existing community-made remixes so that people can see and try what others have created, with each remix listing having...
 +
** The .iso available for download
 +
** The .ks available for download
 +
** A blog or a link to some resource that describes how this remix is being used in a live teaching setting
 +
 +
The page might look something like this:
 +
 +
<pre>
 +
+---------------------------------------------+
 +
|          Unofficial SoaS Remixes          |
 +
|                                            |
 +
| +-----------------+    +---------+---+----+ |
 +
| | SoaS Mango Lassi|    |remix #01|.ks|blog| |
 +
| | summary        |    +---------+---+----+ |
 +
| |                |    |remix #02|.ks|blog| |
 +
| | <link to main  |    +---------+---+----+ |
 +
| | SoaS project    |    |remix foo|.ks|blog| |
 +
| | page>          |    +---------+---+----+ |
 +
| +-----------------+    |remix bar|.ks|blog| |
 +
|                        +---------+---+----+ |
 +
|  description of        | Your remix here! | |
 +
|  remixes, including    |                  | |
 +
|  clear text on how    | Here's how:      | |
 +
|  they are UNSUPPORTED  | <link to Custom- | |
 +
|                        | ization guide>  | |
 +
|                        +------------------+ |
 +
+---------------------------------------------+
 +
</pre>
 +
 +
=== Sample remixes ===
 +
 +
In order to pre-populate the [[#Wiki page]], we would follow the Customization Guide's instruction '''(Draft Content)''' [[Talk:Features/Soas_V4/Remixability#Build_Your_Own_Remix]] to create and post remixes for 2-4 deployments before Mango Lassi's official release date. These would be specific, teacher-driven remixes that would be used in live deployments.
 +
 +
The "blog" link for each of these remixes would go to a description - written either by or in conjunction with the teacher - on why the remix was designed that way, and what their plans for classroom usage are. ("Ms. Smith created this remix for her middle-school Spanish-language classes with the following localization and activities so she could do the following things with Sugar in her syllabus...")
 +
 +
=== Image-building service ===
 +
 +
Provide and advertise an experimental remix image-building service available for the first 2 months after the Mango Lassi release. For this time period, the feature owner takes responsibility for accepting emails with .ks files attached, building the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.
 +
 +
The mechanism of this back-and-forth is up to the feature owner to determine, so long as the mechanism (and the unsupported nature of the remixes generated by it) are clear. The current proposal is as follows:
 +
 +
::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 :
 +
 +
=== Customization guide edits ===
 +
 +
The Customization Guide would be edited to reflect the above changes, and reviewed and tested by a few new remixes for ease-of-use.
  
 
== Benefit to Sugar ==
 
== 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.''
+
Promotes our already-existing technical flexibility to customize Soas-v4 for Deployments and individuals.
 +
 
 +
* add/delete desired applications to standard set on .iso
 +
 
 +
* Targeted uses:
 +
: Multiple Language versions (Including EU Languages?)
 +
: e-book reader
 +
: Older students
 +
: Games
 +
 
 +
*Shared kickstart files e-mailed to SOAS and posted to wiki allow others to learn how to make a .ks file and try various remixes.
 +
*Posted links to a Catalog of prebuilt remix.iso's, with a description of their use and contents, allows less skilled users to use them.
  
 
== Scope ==
 
== 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
+
The technical ability to create remixes has worked for a long time.
 +
: all entries labled xxxx-remix were built using these instructions
  
−
All a User has to do to implement this is to install livecd-tools and spin-kickstarts in their version of fedora:
+
[[Talk:Features/Soas_V4/Install_Test_Table#Test_results]]
  
−
su -c 'yum install livecd-tools spin-kickstarts'
+
The implementation of this feature depends on:
  
−
*And follow instructions.
+
* the editing of the Customization Guide
 +
* the creation a wiki page '''Prototype is here:''' [[Talk:Features/SoaS Remixability]]
 +
* the running of a Remix Image Building Service for 2 months after release
  
 
==UI Design==
 
==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.''
+
 
 +
N/A
  
 
== How To Test ==
 
== How To Test ==
 +
*'''[[Build Your Own Remix with Fedora]]''' latest version (updated 02/08/2011)
 +
 +
:
 +
*depreciated:
 
{{:{{PAGENAME}}/Testing}}
 
{{:{{PAGENAME}}/Testing}}
 +
 
== User Experience ==
 
== 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.''
+
 
 +
Wider choices for users of Soas-v4 due to ability to Customize.
  
 
== Dependencies ==
 
== Dependencies ==
−
''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
+
 
 +
None that I know of.
  
 
== Contingency Plan ==
 
== 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.''
+
Not Needed
  
 
== Documentation ==
 
== Documentation ==
−
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29
+
*'''[[Build Your Own Remix with Fedora]]''' latest version (updated 02/08/2011)
 +
 
 +
older link: [[Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]]
  
 
== Release Notes ==
 
== 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.''
+
None Needed
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
 +
 +
*07/27/2010 Some nice comments from lists:
 +
 +
Caryl Bigenho:
 +
 +
Hi Tom,
 +
I love this idea!  (I hope it would also include easier SoaS creation on the Mac.)  When I lent some of my "Roadshow" library machines to the University of Montana education department to help them prep for a science project, I downloaded a lot of stuff not already there (eg Bridge, Star Chart, etc), then put only them and the essentials (eg Browse, Write, Record) in the favorites and hid all the rest.  It would be really nice to be able to create sticks with special focus like this for targeted projects.
 +
Caryl
 +
 +
Christoph Derndorfer:
 +
 +
wow, this looks like a truly amazing project!
 +
 +
Can't wait to give it a spin at one point or another... :-)
 +
 +
Cheers,
 +
Christoph

Latest revision as of 13:51, 31 January 2014



Summary

The official SoaS image that is released can be used as a base to re-spin custom (unofficial and unsupported) SoaS remixes using the instructions on our official Customization Guide and a few additional FOSS tools outlined in the Guide.

This feature proposes:

  • The development of a page on the SL wiki for highlighting classroom-made remixes, their kickstart files, and details on their usage
  • The creation of 2-4 sample remixes for specific types of classrooms to pre-populate that wiki page
  • An experimental remix image-building service available for the first 2 months after the Mango Lassi release
  • Edits to the Customization Guide version for Mango Lassi that reflect these changes

Owner

  • Email: satellit <at> bendbroadband <dot> com

Current status

Detailed Description

Wiki page

The creation of a page that:

  • Describes remixes
  • Makes it clear that remixes are unsupported
  • Links to the Customization Guide as the canonical resource on how to make remixes
  • Lists existing community-made remixes so that people can see and try what others have created, with each remix listing having...
    • The .iso available for download
    • The .ks available for download
    • A blog or a link to some resource that describes how this remix is being used in a live teaching setting

The page might look something like this: 

+---------------------------------------------+
|           Unofficial SoaS Remixes           |
|                                             |
| +-----------------+    +---------+---+----+ |
| | SoaS Mango Lassi|    |remix #01|.ks|blog| |
| | summary         |    +---------+---+----+ |
| |                 |    |remix #02|.ks|blog| |
| | <link to main   |    +---------+---+----+ |
| | SoaS project    |    |remix foo|.ks|blog| |
| | page>           |    +---------+---+----+ |
| +-----------------+    |remix bar|.ks|blog| |
|                        +---------+---+----+ |
|  description of        | Your remix here! | |
|  remixes, including    |                  | |
|  clear text on how     | Here's how:      | |
|  they are UNSUPPORTED  | <link to Custom- | |
|                        | ization guide>   | |
|                        +------------------+ |
+---------------------------------------------+

Sample remixes

In order to pre-populate the #Wiki page, we would follow the Customization Guide's instruction (Draft Content) Talk:Features/Soas_V4/Remixability#Build_Your_Own_Remix to create and post remixes for 2-4 deployments before Mango Lassi's official release date. These would be specific, teacher-driven remixes that would be used in live deployments.

The "blog" link for each of these remixes would go to a description - written either by or in conjunction with the teacher - on why the remix was designed that way, and what their plans for classroom usage are. ("Ms. Smith created this remix for her middle-school Spanish-language classes with the following localization and activities so she could do the following things with Sugar in her syllabus...")

Image-building service

Provide and advertise an experimental remix image-building service available for the first 2 months after the Mango Lassi release. For this time period, the feature owner takes responsibility for accepting emails with .ks files attached, building the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.

The mechanism of this back-and-forth is up to the feature owner to determine, so long as the mechanism (and the unsupported nature of the remixes generated by it) are clear. The current proposal is as follows:

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 :

Customization guide edits

The Customization Guide would be edited to reflect the above changes, and reviewed and tested by a few new remixes for ease-of-use.

Benefit to Sugar

Promotes our already-existing technical flexibility to customize Soas-v4 for Deployments and individuals.

  • add/delete desired applications to standard set on .iso
  • Targeted uses:
Multiple Language versions (Including EU Languages?)
e-book reader
Older students
Games
  • Shared kickstart files e-mailed to SOAS and posted to wiki allow others to learn how to make a .ks file and try various remixes.
  • Posted links to a Catalog of prebuilt remix.iso's, with a description of their use and contents, allows less skilled users to use them.

Scope

The technical ability to create remixes has worked for a long time.

all entries labled xxxx-remix were built using these instructions

Talk:Features/Soas_V4/Install_Test_Table#Test_results

The implementation of this feature depends on:

  • the editing of the Customization Guide
  • the creation a wiki page Prototype is here: Talk:Features/SoaS Remixability
  • the running of a Remix Image Building Service for 2 months after release

UI Design

N/A

How To Test

  • depreciated:

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

Wider choices for users of Soas-v4 due to ability to Customize.

Dependencies

None that I know of.

Contingency Plan

Not Needed

Documentation

older link: Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29

Release Notes

None Needed

Comments and Discussion

  • 07/27/2010 Some nice comments from lists:

Caryl Bigenho:

Hi Tom, I love this idea! (I hope it would also include easier SoaS creation on the Mac.) When I lent some of my "Roadshow" library machines to the University of Montana education department to help them prep for a science project, I downloaded a lot of stuff not already there (eg Bridge, Star Chart, etc), then put only them and the essentials (eg Browse, Write, Record) in the favorites and hid all the rest. It would be really nice to be able to create sticks with special focus like this for targeted projects. Caryl

Christoph Derndorfer:

wow, this looks like a truly amazing project!

Can't wait to give it a spin at one point or another... :-)

Cheers, Christoph

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Features/SoaS_Remixability&oldid=91317"