8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + − From Caroline Meeks post, 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.+ − − Line 36:
Line 37: + + Line 73:
Line 76: + + + + + + + + Line 78:
Line 89: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
<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.
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 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==
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==
* 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.
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. <br>
- Faster user setup. <br>
-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. <br>
- Communication plan for helping people to get their sugar sticks to boot at
home <br>
-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. <br>
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. <br>
-Grouping collaboration by class on the jabber server (clearly this is for
after we goto Jabber based collaboration.) <br>
-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. <br>
[[Category:Features requested by Gardner Pilot Academy]]
[[Category:Features requested by Gardner Pilot Academy]]