22
edits
Changes
Jump to navigation
Jump to search
Line 53:
Line 53: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 90:
Line 120: − + Line 103:
Line 133: − <!-- Delete this paragraph and the following one when preparing your application. -->Note: you will post this application on the wiki in the category [[:Category:2009 GSoC applications]]. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list(s) (primarily [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] for technical issues and [http://lists.sugarlabs.org/listinfo/iaep It's An Education Project] for educational issues) and/or [[IRC]].+ − − The NeL project has some good general recommendations for [http://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We endorse them all; although Sugar is (regrettably) not test driven development (yet - your project could change that!), we encourage GSoC code to include tests.
→About your project
This implementation need to be done in the core of Sugar and integrated with Journal for data sync.
This implementation need to be done in the core of Sugar and integrated with Journal for data sync.
The big difference with Sugar_on_a_Stick, is that we don't keep the OS in the storage device, sugar_on_a_stick uses an OS very generic
and with grane we avoid that, both have different goals.
Grane will work over Sugar and Sugar over a very customized OS environment for the running hardware. It will be designed to fast-switching between session around different
computers, computer just contain the Sugar environment and sugar-Grane do the dirty tasks. Also it will helps to do a hard copy from one
kid session to another Sugar environment if desired.
* How it should work
The main design of this project involves to patch the Sugar Core, adding the availability to reload different phases of the startup process as requested:
- Read activities lists from given path
- Load journal information using given path
- Set user information
Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:
sugar-grane_unique_user_id/
|
*--> session.info -- Information about the sugar-grane session as id, creation date, last updated, etc
*--> Activities/ -- Full activities
*--> Journal/ -- Journal information
*--> Preferences/ -- User session preferences as colors, name, picture, list of friends, etc
using the proposed structure defined above, when a mass storage device is plugged, Journal will mount the device per default behavior and then
we try to detect if exists a sugar-grane_unique_user_id directory, after validate the session.info file information and if everything is ok, we
launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.
How to create a sugar-grande session in a mass storage device ?, add a 'Mobile' or 'Grane' menu item in the main sugar menu with options
such as export, import, recover, info, etc.
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
[[Image:New-developer-challenge.png|thumb|right|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]
[[Image:New-developer-challenge.png|thumb|right|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]
# We want to make sure that you can set up a [[DevelopmentTeam#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.
# We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.
[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D
[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
not at this moment...
<noinclude>[[Category:2009 GSoC applications]]</noinclude>
<noinclude>[[Category:2009 GSoC applications]]</noinclude>
[[Category:GSoC]]
[[Category:GSoC]]