Archive/Current Events/2008-10-06 - Revision history

KachachanC: Undo revision 99654 by KachachanC (talk)

2016-12-19T13:33:43Z

Undo revision 99654 by KachachanC (talk)

← Older revision		Revision as of 09:33, 19 December 2016
Line 1:		Line 1:
	~~{{Obsolete \| Refer to https://wiki.sugarlabs.org/go/Sugar_Labs/Current_Events for latest current events}}~~
	<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>		<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>

KachachanC at 06:03, 19 December 2016

2016-12-19T06:03:15Z

← Older revision		Revision as of 02:03, 19 December 2016
Line 1:		Line 1:
			{{Obsolete \| Refer to https://wiki.sugarlabs.org/go/Sugar_Labs/Current_Events for latest current events}}
	<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>		<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>

FGrose: moved Sugar Labs/Current Events/Archive/2008-10-06 to Archive/Current Events/2008-10-06: restructure to depopulate Sugar Labs/subpages list

2010-07-27T23:37:48Z

moved Sugar Labs/Current Events/Archive/2008-10-06 to Archive/Current Events/2008-10-06: restructure to depopulate Sugar Labs/subpages list

← Older revision	Revision as of 19:37, 27 July 2010
(No difference)

Patrol: moved Walter is a wanker 9/Current Events/Archive/2008-10-06 to Sugar Labs/Current Events/Archive/2008-10-06 over redirect: revert

2010-02-24T01:42:40Z

moved Walter is a wanker 9/Current Events/Archive/2008-10-06 to Sugar Labs/Current Events/Archive/2008-10-06 over redirect: revert

← Older revision	Revision as of 21:42, 23 February 2010
(No difference)

Page move vandal: moved Sugar Labs/Current Events/Archive/2008-10-06 to Walter is a wanker 9/Current Events/Archive/2008-10-06: Walter is a wanker

2010-02-24T00:19:31Z

moved Sugar Labs/Current Events/Archive/2008-10-06 to Walter is a wanker 9/Current Events/Archive/2008-10-06: Walter is a wanker

← Older revision	Revision as of 20:19, 23 February 2010
(No difference)

Patrol: moved Anal bleaching 11/Current Events/Archive/2008-10-06 to Sugar Labs/Current Events/Archive/2008-10-06 over redirect: revert

2010-02-21T22:34:44Z

moved Anal bleaching 11/Current Events/Archive/2008-10-06 to Sugar Labs/Current Events/Archive/2008-10-06 over redirect: revert

← Older revision	Revision as of 18:34, 21 February 2010
(No difference)

Anal bleaching: moved Sugar Labs/Current Events/Archive/2008-10-06 to Anal bleaching 11/Current Events/Archive/2008-10-06: Anal bleaching

2010-02-21T22:19:49Z

moved Sugar Labs/Current Events/Archive/2008-10-06 to Anal bleaching 11/Current Events/Archive/2008-10-06: Anal bleaching

← Older revision	Revision as of 18:19, 21 February 2010
(No difference)

Dfarning: fix camelcase links

2009-04-08T17:58:17Z

fix camelcase links

← Older revision		Revision as of 13:58, 8 April 2009
Line 21:		Line 21:
	2. LiveUSB: It seems that a LiveUSB offers the most simple way to experience Sugar on a preexisting hardware base, such as a school computer lab. (One advantage of a LiveUSB approach—where user data is stored in a disk partition—is that the same key can be used at school and at home, emulating the experience of a one-to-one laptop program, where the laptops go home with the children. The Fedora team has made progress on a LiveUSB this week (See Item 11 below) and we are also working to get "fresher" Sugar bits into the Ubuntu LiveUSB. However, there remains a problem in that many computers do not have boot-from-USB enabled in the BIOS. Steve Pomeroy suggested we look into U3, a proprietary method of launching applications from a USB key. This would provide a work-around for running Sugar on machines that are running Windows (alas, this accounts for the majority of hardware found in schools). Ben Schwartz pointed out that we could do the same thing using autorun.inf (See [http://www.exponetic.com/blog/blog/2006/07/07/autorun-an-executable-from-a-usb-key-in-windows-xp/ autorun an executable from a USB key in Windows XP]), launching an instance of Sugar in QEMU. Running Sugar in emulation requires a reasonably fast machine in order to give an acceptable experience. We need to do more testing in this arena, as it is a path of least resistance for teachers and parents who are interested in trying Sugar.		2. LiveUSB: It seems that a LiveUSB offers the most simple way to experience Sugar on a preexisting hardware base, such as a school computer lab. (One advantage of a LiveUSB approach—where user data is stored in a disk partition—is that the same key can be used at school and at home, emulating the experience of a one-to-one laptop program, where the laptops go home with the children. The Fedora team has made progress on a LiveUSB this week (See Item 11 below) and we are also working to get "fresher" Sugar bits into the Ubuntu LiveUSB. However, there remains a problem in that many computers do not have boot-from-USB enabled in the BIOS. Steve Pomeroy suggested we look into U3, a proprietary method of launching applications from a USB key. This would provide a work-around for running Sugar on machines that are running Windows (alas, this accounts for the majority of hardware found in schools). Ben Schwartz pointed out that we could do the same thing using autorun.inf (See [http://www.exponetic.com/blog/blog/2006/07/07/autorun-an-executable-from-a-usb-key-in-windows-xp/ autorun an executable from a USB key in Windows XP]), launching an instance of Sugar in QEMU. Running Sugar in emulation requires a reasonably fast machine in order to give an acceptable experience. We need to do more testing in this arena, as it is a path of least resistance for teachers and parents who are interested in trying Sugar.

	3. Teachers/developers: There was a productive discussion on the IAEP list this week about how to better engage teachers in the Sugar developer community. Rob Costello pointed out that only a small percentage of teachers would participate in the actual development process, building bridges to even that small group would be worthwhile. It was pointed out that the [[Activities/Turtle Art/Patching]] (which is still incomplete) is far from meeting the needs of a teacher (or anyone else new to the community). Bill Kerr wrote up some questions that I tried to answer in the wiki (See [[Talk:~~Patching~~ Turtle Art]]):		3. Teachers/developers: There was a productive discussion on the IAEP list this week about how to better engage teachers in the Sugar developer community. Rob Costello pointed out that only a small percentage of teachers would participate in the actual development process, building bridges to even that small group would be worthwhile. It was pointed out that the [[Activities/Turtle Art/Patching]] (which is still incomplete) is far from meeting the needs of a teacher (or anyone else new to the community). Bill Kerr wrote up some questions that I tried to answer in the wiki (See [[Talk:Activities/Turtle Art/Patching]]):

	* Where do you find things (Python files, source code)		* Where do you find things (Python files, source code)

Dfarning: fix link

2009-04-04T00:19:05Z

fix link

← Older revision		Revision as of 20:19, 3 April 2009
Line 21:		Line 21:
	2. LiveUSB: It seems that a LiveUSB offers the most simple way to experience Sugar on a preexisting hardware base, such as a school computer lab. (One advantage of a LiveUSB approach—where user data is stored in a disk partition—is that the same key can be used at school and at home, emulating the experience of a one-to-one laptop program, where the laptops go home with the children. The Fedora team has made progress on a LiveUSB this week (See Item 11 below) and we are also working to get "fresher" Sugar bits into the Ubuntu LiveUSB. However, there remains a problem in that many computers do not have boot-from-USB enabled in the BIOS. Steve Pomeroy suggested we look into U3, a proprietary method of launching applications from a USB key. This would provide a work-around for running Sugar on machines that are running Windows (alas, this accounts for the majority of hardware found in schools). Ben Schwartz pointed out that we could do the same thing using autorun.inf (See [http://www.exponetic.com/blog/blog/2006/07/07/autorun-an-executable-from-a-usb-key-in-windows-xp/ autorun an executable from a USB key in Windows XP]), launching an instance of Sugar in QEMU. Running Sugar in emulation requires a reasonably fast machine in order to give an acceptable experience. We need to do more testing in this arena, as it is a path of least resistance for teachers and parents who are interested in trying Sugar.		2. LiveUSB: It seems that a LiveUSB offers the most simple way to experience Sugar on a preexisting hardware base, such as a school computer lab. (One advantage of a LiveUSB approach—where user data is stored in a disk partition—is that the same key can be used at school and at home, emulating the experience of a one-to-one laptop program, where the laptops go home with the children. The Fedora team has made progress on a LiveUSB this week (See Item 11 below) and we are also working to get "fresher" Sugar bits into the Ubuntu LiveUSB. However, there remains a problem in that many computers do not have boot-from-USB enabled in the BIOS. Steve Pomeroy suggested we look into U3, a proprietary method of launching applications from a USB key. This would provide a work-around for running Sugar on machines that are running Windows (alas, this accounts for the majority of hardware found in schools). Ben Schwartz pointed out that we could do the same thing using autorun.inf (See [http://www.exponetic.com/blog/blog/2006/07/07/autorun-an-executable-from-a-usb-key-in-windows-xp/ autorun an executable from a USB key in Windows XP]), launching an instance of Sugar in QEMU. Running Sugar in emulation requires a reasonably fast machine in order to give an acceptable experience. We need to do more testing in this arena, as it is a path of least resistance for teachers and parents who are interested in trying Sugar.

	3. Teachers/developers: There was a productive discussion on the IAEP list this week about how to better engage teachers in the Sugar developer community. Rob Costello pointed out that only a small percentage of teachers would participate in the actual development process, building bridges to even that small group would be worthwhile. It was pointed out that the [[~~Patching~~ Turtle Art]] (which is still incomplete) is far from meeting the needs of a teacher (or anyone else new to the community). Bill Kerr wrote up some questions that I tried to answer in the wiki (See [[Talk:Patching Turtle Art]]):		3. Teachers/developers: There was a productive discussion on the IAEP list this week about how to better engage teachers in the Sugar developer community. Rob Costello pointed out that only a small percentage of teachers would participate in the actual development process, building bridges to even that small group would be worthwhile. It was pointed out that the [[Activities/Turtle Art/Patching]] (which is still incomplete) is far from meeting the needs of a teacher (or anyone else new to the community). Bill Kerr wrote up some questions that I tried to answer in the wiki (See [[Talk:Patching Turtle Art]]):

	* Where do you find things (Python files, source code)		* Where do you find things (Python files, source code)

Dfarning: fix camelcase links

2009-04-03T22:26:15Z

fix camelcase links

← Older revision		Revision as of 18:26, 3 April 2009
Line 75:		Line 75:
	16. Etoys project sharing: Daniel Ajoy inquired about uploading Etoys projects to the Internet. While the "core" Etoys team doesn't have a world-writable project-sharing site, they do recommend tools for setting up regional sites. To set up your own server, the simplest thing is to set up the [http://swikis.ddo.jp/SuperSwiki2/3 SuperSwiki2 server].		16. Etoys project sharing: Daniel Ajoy inquired about uploading Etoys projects to the Internet. While the "core" Etoys team doesn't have a world-writable project-sharing site, they do recommend tools for setting up regional sites. To set up your own server, the simplest thing is to set up the [http://swikis.ddo.jp/SuperSwiki2/3 SuperSwiki2 server].

	17. Debian jhbuild: The Debian team has done a thorough job of documenting the process of building a Sugar environment on a Debian GNU/Linux distribution (See [[~~DevelopmentTeam~~/Jhbuild/Debian]]).		17. Debian jhbuild: The Debian team has done a thorough job of documenting the process of building a Sugar environment on a Debian GNU/Linux distribution (See [[Development Team/Jhbuild/Debian]]).

	=== Sugar Labs ===		=== Sugar Labs ===