User:MartinDengler/Commentaries:SoaSonXO - Revision history

Mstone: /* OLPC-like update mechanism */

2009-04-22T11:55:04Z

OLPC-like update mechanism

← Older revision		Revision as of 07:55, 22 April 2009
Line 25:		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].		* 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 ==

MartinDengler: /* Discussion Items */

2009-04-21T00:44:08Z

Discussion Items

← Older revision		Revision as of 20:44, 20 April 2009
Line 19:		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) ~~via~~ wireless drivers?		* 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.

MartinDengler: /* OLPC-like update mechanism */

2009-04-21T00:43:09Z

OLPC-like update mechanism

← Older revision		Revision as of 20:43, 20 April 2009
Line 25:		Line 25:
	=== OLPC-like update mechanism ===		=== OLPC-like update mechanism ===

	* ~~Keep in mind~~ [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|~~some~~ olpc-update ~~goals~~]] ~~which I believe are~~ still [http://dev.laptop.org/git/projects/olpc-update/\|being ~~worked upon~~].		* 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 ==

MartinDengler at 00:31, 21 April 2009

2009-04-21T00:31:39Z

← Older revision		Revision as of 20:31, 20 April 2009
Line 25:		Line 25:
	=== OLPC-like update mechanism ===		=== OLPC-like update mechanism ===

	* Keep in mind [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|some olpc-update goals]] which I believe are still [[http://dev.laptop.org/git/projects/olpc-update/\|being worked upon]].		* Keep in mind [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|some olpc-update goals]] which I believe are still [http://dev.laptop.org/git/projects/olpc-update/\|being worked upon].

	== Background ==		== Background ==
Line 39:		Line 39:
	=== Sugar on a Stick ===		=== Sugar on a Stick ===

	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).		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).

	* Release date: (see [[]])
	* 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 49:		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)		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
	* codename: unknown.

	== Original IRC Discussion ==		== Original IRC Discussion ==

MartinDengler at 00:29, 21 April 2009

2009-04-21T00:29:26Z

← Older revision		Revision as of 20:29, 20 April 2009
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 37:		Line 39:
	=== Sugar on a Stick ===		=== Sugar on a Stick ===

	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).		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).

	* Release date: (see [[]])		* Release date: (see [[]])

MartinDengler: /* Background */

2009-04-21T00:26:58Z

Background

← Older revision		Revision as of 20:26, 20 April 2009
Line 34:		Line 34:

	* 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.

	~~=== General ===~~

	=== Sugar on a Stick ===		=== Sugar on a Stick ===

MartinDengler: /* Background */

2009-04-21T00:26:37Z

Background

← Older revision		Revision as of 20:26, 20 April 2009
Line 34:		Line 34:

	* 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.


	=== General ===		=== General ===
Line 56:		Line 55:
	* Rawhide XO target software: Fedora 12, Sugar 0.86		* Rawhide XO target software: Fedora 12, Sugar 0.86
	* codename: unknown.		* codename: unknown.


	== Original IRC Discussion ==		== Original IRC Discussion ==

MartinDengler at 00:22, 21 April 2009

2009-04-21T00:22:33Z

← Older revision		Revision as of 20:22, 20 April 2009
Line 1:		Line 1:

	== Some Discussion on SoaS and using it on the XO ==		== Some Discussion on SoaS and using it on the XO ==

	'''Can I get SoaS on my XO''' is a FAQ without a ~~clear~~ answer.		'''Can I get SoaS on my XO?''' is a FAQ without a simple answer.

	[[#Original_IRC_Discussion\|An IRC discussion on #sugar]] raised the [[#Discussion_Items\|following questions for discussion]]:		[[#Original_IRC_Discussion\|An IRC discussion on #sugar]] raised the [[#Discussion_Items\|following questions for discussion]]:
Line 25:		Line 24:

	* Keep in mind [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|some olpc-update goals]] which I believe are still [[http://dev.laptop.org/git/projects/olpc-update/\|being worked upon]].		* Keep in mind [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|some olpc-update goals]] which I believe are still [[http://dev.laptop.org/git/projects/olpc-update/\|being worked upon]].


	== Background ==		== Background ==

MartinDengler at 00:21, 21 April 2009

2009-04-21T00:21:48Z

← Older revision		Revision as of 20:21, 20 April 2009
Line 1:		Line 1:

	== Some Discussion on SoaS and using it on the XO ==		== Some Discussion on SoaS and using it on the XO ==

	Can I get SoaS ~~(or "the latest Sugar")~~ on my XO is a FAQ without a clear answer. ~~[[#Original_IRC_Discussion\|an IRC discussion on #sugar]] raised the [[#Discussion_Items\|following questions for discussion]]:~~		'''Can I get SoaS on my XO''' is a FAQ without a clear answer.

			[[#Original_IRC_Discussion\|An IRC discussion on #sugar]] raised the [[#Discussion_Items\|following questions for discussion]]:

	== Discussion Items ==		== Discussion Items ==
Line 13:		Line 15:

	:This section is intentionally not titled "jffs2 images".		:This section is intentionally not titled "jffs2 images".


	=== non-Fedora bits ===		=== non-Fedora bits ===
Line 20:		Line 21:

	: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.


	=== OLPC-like update mechanism ===		=== OLPC-like update mechanism ===

MartinDengler: add olpc-update commentary

2009-04-21T00:20:44Z

add olpc-update commentary

← Older revision		Revision as of 20:20, 20 April 2009
Line 20:		Line 20:

	: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.


			=== OLPC-like update mechanism ===

			* Keep in mind [[OLPC:User:Mstone/Commentaries/Mass olpc-update\|some olpc-update goals]] which I believe are still [[http://dev.laptop.org/git/projects/olpc-update/\|being worked upon]].


	== Background ==		== Background ==