Sugar on a Stick/Goals - Revision history

FGrose at 22:44, 1 November 2009

2009-11-01T22:44:02Z

← Older revision		Revision as of 18:44, 1 November 2009
Line 1:		Line 1:
	<noinclude>~~{{GoogleTrans-en}}~~{{TeamHeader\|Sugar on a Stick\|home=Project Home\|xbgColor=ffe792\|join_label=Get Involved}}{{TOCright}}</noinclude>		<noinclude>{{TeamHeader\|Sugar on a Stick\|home=Project Home\|xbgColor=ffe792\|join_label=Get Involved}}{{TOCright}}</noinclude>
			==Introduction==
			See [[../Resources]] for some background on the project and a description of the core goals.

	~~From~~ Caroline Meeks ~~post~~, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05998.html		In July 2009, Caroline Meeks posted some goals for v2 SoaS, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05998.html:
			:I am going to try to answer this, or actually I hope start a brainstorming session that will get us towards a feature list.

	~~I am going to try to answer this, or actually I hope start a brainstorming session that will get us towards a feature list.~~		:I am going to try to use the Customer Role of an Agile process. That means I'm going to try to talk as much about the result I want to see as I can and as little as I can about how to get to it. I do know that some of this is in the works. I also know that some of it will require the heavens to deliver us yet another genius programmer with a new skill set to accomplish by September. But the job of the role of Customer in my mind is to talk about what I'd like to see, what the business case for it is, and what the priority is. I hope other people will join me in this role as I think it's crucial information for the technical team to have.

	I am going to try to use the Customer Role of an Agile process. That means I'm going to try to talk as much about the result I want to see as I can and as little as I can about how to get to it. I do know that some of this is in the works. I also know that some of it will require the heavens to deliver us yet another genius programmer with a new skill set to accomplish by September. But the job of the role of Customer is my mind is to talk about what I'd like to see, what the business case for it is and what the priority is. I hope other people will join me in this role as i think ~~its~~ crucial information for the technical team to have.

	==Types of Requests==		==Types of Requests==

Gregorio: /* Solid Collaboration */

2009-07-21T14:30:01Z

Solid Collaboration

← Older revision		Revision as of 10:30, 21 July 2009
Line 36:		Line 36:

	The GPA school will use option 1 above. It will also use local collaboration with no Jabber server. [[User:Gregorio\|Gregorio]] 13:20, 21 July 2009 (UTC)		The GPA school will use option 1 above. It will also use local collaboration with no Jabber server. [[User:Gregorio\|Gregorio]] 13:20, 21 July 2009 (UTC)

			This feature should still be tracked for the fall so that kids can collaborate from home. In that case number above will be used.

	==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==		==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==

Gregorio: /* Incoming Ideas */

2009-07-21T14:29:10Z

Incoming Ideas

Gregorio at 14:24, 21 July 2009

2009-07-21T14:24:09Z

← Older revision		Revision as of 10:24, 21 July 2009
Line 86:		Line 86:

	So I hope everyone else sticks their necks out and says what features they want, what the use cases are and what they think their relative importance are. Then we can narrow our focus back down to what we can do for September.		So I hope everyone else sticks their necks out and says what features they want, what the use cases are and what they think their relative importance are. Then we can narrow our focus back down to what we can do for September.

			==Incoming Ideas==

			Parking this e-mail here until I can analyze it and break it out in to features. [[User:Gregorio\|Gregorio]] 14:24, 21 July 2009 (UTC)
			http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016909.html

			For the fall - here is a brainstorm

			- Reliably working on the Macbooks in the laptop cart.
			- Faster user setup.
			-Easier setup in the computer lab - We can try upgrading the BIOS and see if
			we can get it to boot directly from USB. We could have a floppy boot helper
			that could just stay with the computer.
			- Communication plan for helping people to get their sugar sticks to boot at
			home
			-More robust sticks, I think there is a ticket in on the goes to user login
			but with no user name but we've seen on a few sticks now.

			I think the 4 items above will all be much easier if we are using a stick
			format where you can see the files rather then one squash image file. there
			is at least one ticket in for that. I'd like some technical opinions on
			that, but my sense is the underlying reformat of the stick is what should be
			to top priority item.


			-Prettier reboot. Reboot takes you to a nonsugar screen where you have to
			press return when it says user name is liveuser. Sometimes it fails
			completely as above.
			-Grouping collaboration by class on the jabber server (clearly this is for
			after we goto Jabber based collaboration.)
			-Teacher collecting homework and assessing workflow. Right now it looks like
			the fall early adopters will be doing a lot of writing so think of a student
			writing an essay and the teacher being able to take all those essays home,
			read and comment on them, and return them.


	[[Category:Features requested by Gardner Pilot Academy]]		[[Category:Features requested by Gardner Pilot Academy]]

Gregorio at 14:03, 21 July 2009

2009-07-21T14:03:39Z

← Older revision		Revision as of 10:03, 21 July 2009
Line 73:		Line 73:
	* Priority C for Sugar		* Priority C for Sugar

			==Better Paint Program==
			The Paint program was very slow at GPA. It especially slowed down when trying to fill or draw shapes.

			See more discussion on improvements needed here: http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016344.html

			A new paint program (e.g. TuxPaint) or fixes to the existing one will both be considered.

			==Original e-mail ending==
	I am copying the Server list because I think many of the things I think are the most important next steps for Sugar require interfacing with, and improvements in the XS.		I am copying the Server list because I think many of the things I think are the most important next steps for Sugar require interfacing with, and improvements in the XS.

Gregorio: /* Types of Requests */

2009-07-21T13:58:04Z

Types of Requests

← Older revision		Revision as of 09:58, 21 July 2009
Line 14:		Line 14:

	The first are barriers and bugs to executing the desired lesson plans. The second are tools and technologies to manage many students and allow them to work together. The major headigs below fall in to the second category. We should add any lesson specific bugs or features here as well.		The first are barriers and bugs to executing the desired lesson plans. The second are tools and technologies to manage many students and allow them to work together. The major headigs below fall in to the second category. We should add any lesson specific bugs or features here as well.

			For lesson specific features priority will be given to the following kinds of issues:
			* SW is hard to explain and/or its not discoverable so kids need 1 - 1 help.
			* SW is time consuming, slow or requires too many clicks.
			* Something we want to do is not possible.
			* New or updated activity is needed.
			* Crash or failure to perform as intended, especially if it entails data loss.
			* Class management is too time consuming for the teacher.

			Time is extremely precious in class. You get one hour with the kids so every second counts. If something is not clear to kids and you have to explain it to each kid or touch each computer, that is very costly. If it takes 1 minute to show a kid how to do something, there are 20 kids and you have lost 1/3 of your class!

	==Solid Collaboration==		==Solid Collaboration==

Gregorio at 13:20, 21 July 2009

2009-07-21T13:20:16Z

← Older revision		Revision as of 09:20, 21 July 2009
Line 6:		Line 6:

	I am going to try to use the Customer Role of an Agile process. That means I'm going to try to talk as much about the result I want to see as I can and as little as I can about how to get to it. I do know that some of this is in the works. I also know that some of it will require the heavens to deliver us yet another genius programmer with a new skill set to accomplish by September. But the job of the role of Customer is my mind is to talk about what I'd like to see, what the business case for it is and what the priority is. I hope other people will join me in this role as i think its crucial information for the technical team to have.		I am going to try to use the Customer Role of an Agile process. That means I'm going to try to talk as much about the result I want to see as I can and as little as I can about how to get to it. I do know that some of this is in the works. I also know that some of it will require the heavens to deliver us yet another genius programmer with a new skill set to accomplish by September. But the job of the role of Customer is my mind is to talk about what I'd like to see, what the business case for it is and what the priority is. I hope other people will join me in this role as i think its crucial information for the technical team to have.

			==Types of Requests==
			[[User:Gregorio\|Gregorio]] 13:20, 21 July 2009 (UTC) <br>
			I suggest we break out feature requests in to two types:
			# Lesson specific facilitators
			# Class management

			The first are barriers and bugs to executing the desired lesson plans. The second are tools and technologies to manage many students and allow them to work together. The major headigs below fall in to the second category. We should add any lesson specific bugs or features here as well.

	==Solid Collaboration==		==Solid Collaboration==
Line 12:		Line 20:

	* Four network configurations are envisioned for use of this feature at GPA:		* Four network configurations are envisioned for use of this feature at GPA:
	# Computers on same LAN segment ~~See related http://dev.sugarlabs.org/ticket/1012~~		# Computers on same LAN segment
	# Computers on same LAN no VLAN or bridge segment restrictions (aka bug 1012 resolved).		# Computers on same LAN no VLAN or bridge segment restrictions (aka bug 1012 resolved).
	# Computers IP connected to a server inside the firewall only. e.g. School Server in school.		# Computers IP connected to a server inside the firewall only. e.g. School Server in school.
	# Computers anywhere on the Internet accessing publicly addressable school server (or any Jabber implementation)		# Computers anywhere on the Internet accessing publicly addressable school server (or any Jabber implementation)

			The GPA school will use option 1 above. It will also use local collaboration with no Jabber server. [[User:Gregorio\|Gregorio]] 13:20, 21 July 2009 (UTC)

	==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==		==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==

CarolineM: /* Avoid surplus Activity launching */

2009-07-16T01:32:23Z

Avoid surplus Activity launching

← Older revision		Revision as of 21:32, 15 July 2009
Line 47:		Line 47:

	==Avoid surplus Activity launching==		==Avoid surplus Activity launching==
	Don't let the user keep opening activities until the machine crashes or is driven to its knees.		Don't let the user keep opening activities until the machine crashes or is driven to its knees. Make it less likely that a user who is impatient will end up opening multiple copies of an activity.
	* Priority C for GPA		* Priority C for GPA

Skierpage: add Category:Features requested by Gardner Pilot Academy, though this isn't the best way to do it

2009-07-07T23:50:42Z

add Category:Features requested by Gardner Pilot Academy, though this isn't the best way to do it

← Older revision		Revision as of 19:50, 7 July 2009
Line 58:		Line 58:

	So I hope everyone else sticks their necks out and says what features they want, what the use cases are and what they think their relative importance are. Then we can narrow our focus back down to what we can do for September.		So I hope everyone else sticks their necks out and says what features they want, what the use cases are and what they think their relative importance are. Then we can narrow our focus back down to what we can do for September.

			[[Category:Features requested by Gardner Pilot Academy]]

Gregorio: /* Solid Collaboration */

2009-07-07T14:16:30Z

Solid Collaboration

← Older revision		Revision as of 10:16, 7 July 2009
Line 10:		Line 10:
	* Priority A for [[Gardner Pilot Academy\|GPA Project]]. - Defining what this looks like and how we get there is an important discussion and i don't have all those answers. This encompasses local and jabber collaboration.		* Priority A for [[Gardner Pilot Academy\|GPA Project]]. - Defining what this looks like and how we get there is an important discussion and i don't have all those answers. This encompasses local and jabber collaboration.
	* Priority(?) Switch on sugar control panel to turn on/off jabber and use only local network for collaboration [satellit07/05/2009]		* Priority(?) Switch on sugar control panel to turn on/off jabber and use only local network for collaboration [satellit07/05/2009]

			* Four network configurations are envisioned for use of this feature at GPA:
			# Computers on same LAN segment See related http://dev.sugarlabs.org/ticket/1012
			# Computers on same LAN no VLAN or bridge segment restrictions (aka bug 1012 resolved).
			# Computers IP connected to a server inside the firewall only. e.g. School Server in school.
			# Computers anywhere on the Internet accessing publicly addressable school server (or any Jabber implementation)

	==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==		==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==

← Older revision		Revision as of 10:29, 21 July 2009
Line 94:		Line 94:
	For the fall - here is a brainstorm		For the fall - here is a brainstorm

	- Reliably working on the Macbooks in the laptop cart.		- Reliably working on the Macbooks in the laptop cart. <br>
	- Faster user setup.		- Faster user setup. <br>
	-Easier setup in the computer lab - We can try upgrading the BIOS and see if		-Easier setup in the computer lab - We can try upgrading the BIOS and see if
	we can get it to boot directly from USB. We could have a floppy boot helper		we can get it to boot directly from USB. We could have a floppy boot helper
	that could just stay with the computer.		that could just stay with the computer. <br>
	- Communication plan for helping people to get their sugar sticks to boot at		- Communication plan for helping people to get their sugar sticks to boot at
	home		home <br>
	-More robust sticks, I think there is a ticket in on the goes to user login		-More robust sticks, I think there is a ticket in on the goes to user login
	but with no user name but we've seen on a few sticks now.		but with no user name but we've seen on a few sticks now. <br>

	I think the 4 items above will all be much easier if we are using a stick		I think the 4 items above will all be much easier if we are using a stick
Line 113:		Line 113:
	-Prettier reboot. Reboot takes you to a nonsugar screen where you have to		-Prettier reboot. Reboot takes you to a nonsugar screen where you have to
	press return when it says user name is liveuser. Sometimes it fails		press return when it says user name is liveuser. Sometimes it fails
	completely as above.		completely as above. <br>
	-Grouping collaboration by class on the jabber server (clearly this is for		-Grouping collaboration by class on the jabber server (clearly this is for
	after we goto Jabber based collaboration.)		after we goto Jabber based collaboration.) <br>
	-Teacher collecting homework and assessing workflow. Right now it looks like		-Teacher collecting homework and assessing workflow. Right now it looks like
	the fall early adopters will be doing a lot of writing so think of a student		the fall early adopters will be doing a lot of writing so think of a student
	writing an essay and the teacher being able to take all those essays home,		writing an essay and the teacher being able to take all those essays home,
	read and comment on them, and return them.		read and comment on them, and return them. <br>


	[[Category:Features requested by Gardner Pilot Academy]]		[[Category:Features requested by Gardner Pilot Academy]]