User:MartinDengler/Commentaries:SoaSonXO: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{TOCright}} | |||
== Some Discussion on SoaS and using it on the XO == | == Some Discussion on SoaS and using it on the XO == | ||
| Line 17: | Line 19: | ||
=== non-Fedora bits === | === non-Fedora bits === | ||
* Should Soas2's software artifacts include non-Fedora (that is, non-upstream) bits or yum repositories? For example: a) OLPC kernel (2.6.25); or b) | * Should Soas2's software artifacts include non-Fedora (that is, non-upstream) bits or yum repositories? For example: a) OLPC kernel (2.6.25); or b) Via wireless drivers? | ||
:Though (and this is potentially a big "though") these bits/repos must be supported by SugarLabs without any upstream assistance (this statement is a bit less equivocal than strictly necessary), they would provide a solution with a lot more working features. For example, it's hard to imagine an accepted XO-1 solution without power management, or an accepted Eee (is that Via???) solution without wireless. However, these may not be enough of SoaS's target audience to merit the additional work. | :Though (and this is potentially a big "though") these bits/repos must be supported by SugarLabs without any upstream assistance (this statement is a bit less equivocal than strictly necessary), they would provide a solution with a lot more working features. For example, it's hard to imagine an accepted XO-1 solution without power management, or an accepted Eee (is that Via???) solution without wireless. However, these may not be enough of SoaS's target audience to merit the additional work. | ||
| Line 23: | Line 25: | ||
=== OLPC-like update mechanism === | === OLPC-like update mechanism === | ||
* | * Should an [[OLPC:User:Mstone/Commentaries/Mass olpc-update|olpc-update-like]] mechanism be supported? This is quite a lot of work. There is still some [http://dev.laptop.org/git/projects/olpc-update/ work being done on olpc-update]. | ||
== Background == | == Background == | ||
| Line 34: | Line 36: | ||
* Soas2 and Rawhide-XO are built at different times by different groups, and this is expected to continue. | * Soas2 and Rawhide-XO are built at different times by different groups, and this is expected to continue. | ||
=== Sugar on a Stick === | === Sugar on a Stick === | ||
Codename: ''SoaS''. See more about goals at [[ | Codename: ''SoaS''. See more about goals at [[Sugar_on_a_Stick/Project_Goals]]. Target audience: USB-stick instances of Sugar that are portable among different computers. Also used to refer to the *next* version of Sugar on a Stick (as opposed to *any future* version). | ||
* SoaS target hardware: anything supported by Fedora 11 (and exactly Fedora 11 - for example XO-1s will run SoaS but, currently, without OLPC's power management and mesh networking patches. See the Discussion section below.) | * SoaS target hardware: anything supported by Fedora 11 (and exactly Fedora 11 - for example XO-1s will run SoaS but, currently, without OLPC's power management and mesh networking patches. See the Discussion section below.) | ||
* SoaS current software: Fedora 11; Sugar 0.84 | * SoaS current software: Fedora 11; Sugar 0.84 | ||
| Line 50: | Line 48: | ||
=== Rawhide XO === | === Rawhide XO === | ||
Latest OLPC software spin. See more about goals at [[OLPC:Rawhide-XO]]. "Rawhide-XO" also refers to the as-yet-unnamed next OLPC release for the XO-1 (all details TBD, including target hardware) | |||
* Rawhide XO target hardware: XO-1, XO-1.5 | * Rawhide XO target hardware: XO-1, XO-1.5 | ||
* Rawhide XO current software: snapshots based on Rawhide, approaching F11 | * Rawhide XO current software: snapshots based on Rawhide, approaching F11 | ||
* Rawhide XO target software: Fedora 12, Sugar 0.86 | * Rawhide XO target software: Fedora 12, Sugar 0.86 | ||