Sugar Labs - User contributions [en]

Summer of Code/Interviews

2009-04-14T14:19:14Z

Edsiper: /* Wed Apr 15 */

We would like to interview the candidates for Google Summer of Code under Sugar Labs. Please sign up for a time below. If you have been told the name of your provisional prospective mentor, and your mentor has put his/her preferred times below, please try to find a time which works for your mentor. (Note that mentor assignments are still in flux; if your provisional prospective mentor changes, we will try to accommodate your chosen time or reschedule at a convenient time for you.)

Interviews will be conducted over IRC; even hours on #sugar-interview0 and half-hours on #sugar-interview1 . Please treat these like real rooms, ie, do not lurk unless you are a mentor. If you have some quick pre-interview questions, we will be in #sugar too.

If you have specifically been told to sign up to interview, please sign up here. Even if your provisional prospective mentor has not indicated availability, put your available times, and your mentor will renegotiate with you later if necessary. We have invited the 9-10 proposals which are currently ranked highest, for the 4-6 slots we will probably get. However, we ''do'' want to interview you even if you have not specifically been invited; although your proposal is a long shot in that case, you may impress us, and in any case we'd like to talk to you about participating in Sugar outside of GSoC.

Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of the applications we've received are things that we'd really love to have you working on, even if we don't have space for you in GSoC. If you are interested in finishing your project and would like a mentor assigned even though we can't give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we'll work something out.

== Sunday Apr 1 ==

Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...

* [http://www.timeanddate.com/counters/customcounter.html?day=1&month=04&year=2009&hour=14&min=0&sec=0&p0=0 1400 UTC]: [[User:example|example]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example - I used <nowiki>~~~~</nowiki> to add a signature, and added any special requests after.)

== Wed Apr 15 ==

Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira, [[User:Aa|aa]], [[User:Tomeu|Tomeu]], ...

* [http://www.timeanddate.com/counters/customcounter.html?day=15&month=04&year=2009&hour=14&min=0&sec=0&p0=0 1400 UTC]: Vamsi Krishna Davuluri (iwikiwi)

* 1430 UTC: Eduardo Silva (edsiper)

* 1500 UTC: Lucian Branescu (lucian1900)

* 1530 UTC:

== Thurs Apr 16 (Wed 15 in the western hemisphere) ==

Mentors attending: Jameson Quinn, [[User:Aa|aa]], [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...

* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=0&min=0&sec=0&p0=0 0000 UTC]:Felipe López Toledo (subzero)

* 0030 UTC:

* 0100 UTC:

* 0130 UTC:

== Thurs Apr 16 ==

Mentors attending: Jameson Quinn, Sayamindu Dasgupta, Assim Deodia, [[User:Tomeu|Tomeu]], ...

* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=18&min=0&sec=0&p0=0 1800 UTC]:

* 1830 UTC:

* 1900 UTC:

* 1930 UTC:

Sugar Grane

2009-04-12T15:01:14Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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.

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-12T14:58:58Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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 'Portable' item in the main sugar menu with options to export, import, recover, 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.

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-12T14:55:30Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-12T14:45:36Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-12T14:44:36Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-12T14:38:07Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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 current user information

- Activities: Sugar read two main directories to get the activities list and then it build on fly the launcher for each one,

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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 [[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

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-03T18:37:07Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.

[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-03T18:33:56Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.

[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-03T18:32:12Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

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 grain we avoid that. Grane will 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.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.

[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-03T18:05:33Z

Edsiper: /* Miscellaneous */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.

[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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>

[[Category:GSoC]]

Sugar Grane

2009-04-03T18:01:41Z

Edsiper: /* Miscellaneous */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.

[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
M

# Describe a great learning experience you had as a child.
Long time ago...when I was a child my clock stop to work, I decide to open it and do something, I just remove like 8 pieces, when I assembly again it continue not working and 2 pieces continue on my other hand, the conclusion was: try to fix, try to discover, but sometimes you cannot do things by your own alone, try to ask or get some help some times.

# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:54:44Z

Edsiper: /* You and the community */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue their work/game from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:53:45Z

Edsiper: /* You and the community */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always
could continue from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:52:28Z

Edsiper: /* You and the community */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

# The Sugar-data of each child will be portable and easily to load in a Sugar environment, this will impact in a positive way to childs who do not own a laptop and always could continue from there were the last time.

# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
I would like to be involved on this, I have a couple of ideas and some contacts with organizations, I think that we could discuss this in private in first instance.

# What will you do if you get stuck on your project and your mentor isn't around?
Sugar Labs is a community, I would contact other SL-SoC mentors or discuss my issue in the mailing list/IRC...etc

# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
Communication is the, mailing list is the best way to keep the community informed about the project progress

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:45:20Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

# Apr 20: Know mentor, discuss about the project
# Apr 27: Identify Sugar core areas which will need to be modified
# May 04: Propose on-fly sugar configuration paths
# May 18: Create "backup package" process,it will cover activities and journal data
# Jun 15: Submit patches for Sugar-Grane load interface: graned-storage-device-detect, start sugar session based on graned version.
# Jul 06: Bug fixing, Q/A, first official release

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and working globally.
# I'm very creative and I like to collaborate
# Contribute in open source is very attractive to me, I've been involved for years and I would be glad to participate as third time for Sugar-Labs.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
# What will you do if you get stuck on your project and your mentor isn't around?
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:29:37Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

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

* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# I have completed successfully two Summer of Code with OLPC/Sugar
# I've been involved in educational areas for years, working in children communities through the YMCA.
# I've the required skills for design, programming and work in a collaborative way.
#

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
# What will you do if you get stuck on your project and your mentor isn't around?
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:26:34Z

Edsiper: /* About your project */

Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application.

Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.

{{TOCright}}

====About you====

* What is your name?
Eduardo Silva Pereira

* What is your email address?
edsiper@gmail.com

* What is your Sugar Labs wiki username?
edsiper

* What is your IRC nickname?
edsiper

* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
Spanish

* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
Chile, available to work from 19:30 EST

* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
I've been using linux during the last 10 years, as end user, system administrator and developer.

In 2001 I started to contribute to the open source world, I created a project called "Monkey HTTP Daemon", a
small and fast web server for Linux written in C.

Also I had contributed to the One Laptop Per Child (OLPC) project through GSoC 2006, developing a resource usage tool for Linux called Memphis, where we focus on
quantify CPU, X, memory usage among with other metrics. On 2007 I got involved in OLPC again through GSoC but on these time directly contributing to the UI
interface called Sugar, where I was helping to develop the graphic toolkit and contributing with different activities as the developer console, log viewer, terminal,
irc client and others.

Every year I dedicate some time to participate in national/International conferences as speaker trying to motivate others to participate.

A resume of my code contributions can be found here:

[http://www.ohloh.net/accounts/edsiper?ref=Detailed http://www.ohloh.net/accounts/edsiper?ref=Detailed]

====About your project====

* What is the name of your project?
Sugar-Grane

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
Kids do not bring a laptop or computer on his bag every day, Sugar-Grane is a new sugar core feature will allow to the kids to sync his session+activities+personal_data
in a mobile storage device as an USB Key, after that the kid can plug his storage device in another Sugar running and it will change to the Graned session, on that way
Sugar becomes a more powerful educational core providing the option to kids which do not own a laptop feels like to have one when plug their Sugar-Grane.

This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

# 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.
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

====You and the community====

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
# What will you do if you get stuck on your project and your mentor isn't around?
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

====Miscellaneous====
[[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.
# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
# Describe a great learning experience you had as a child.
# 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?

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.

<noinclude>[[Category:2009 GSoC applications]]</noinclude>

[[Category:GSoC]]

Sugar Grane

2009-04-03T17:17:35Z

Edsiper: /* About you */

Sugar Grane

2009-04-03T17:16:09Z

Edsiper: /* About you */

Sugar Grane

2009-04-03T17:15:40Z

Edsiper: /* About you */

Sugar Grane

2009-04-03T17:14:37Z

Edsiper: New page: Please apply also in [http://socghop.appspot.com melange, google's web app]; if you do not apply there '''before''' April 3, we will not be able to accept your application. Please keep an...

Development Team/Almanac/Activity Bundles

2007-11-14T02:55:01Z

Edsiper: /* .info File Format */

{{OLPC}}
{{Translations}}
== Introduction ==

Every activity in the [[Sugar]] environment is packaged into a self-contained '''"bundle"'''. The bundle contains all the resources and executable code (other than system-provided base libraries) which the activity needs to execute. Any resources or executable code that is not provided by the base system must be packaged within the bundle.
; See also : [[OLPC Bitfrost]] in general and its section on [[OLPC Bitfrost#Software installation|software installation]]
: [[OLPC Human Interface Guidelines/Activities|HIG-Activities]] and its section on [[OLPC Human Interface Guidelines/Activities/Activity Bundles|activity bundles]]
: '''[[Creating_an_Activity|Creating an Activity bundle]]

== Rationale ==

Activities are meant to be shared between children. If a child doesn't have the activity, it is automatically transfered to the child when he or she joins the shared activity. Packaging activities in self-contained bundles allows easy sharing, installation, removal, and backup.

== Location ==

Activities are installed and removed automatically by [[Sugar]], in response to user actions. Sugar places activities in directory of its choice. Activities should not rely on being installed in a specific location, and should use relative paths where paths are necessary (i.e., for shared library linkage, activity resources such as images, sounds, etc). They should also not rely on the bundle's base directory name remaining the same. Sugar may rename the activity bundle base directory at any time to prevent bundle conflicts.

Currently Sugar on jhbuild looks for bundles in the "activities" subfolders of XDG_DATA_DIRS. Right now this is /usr/share/activities and the usr/share/activities subfolder of the jhbuild build folder.

Sugar will automatically generate and remove the .service files necessary to launch the activity through D-Bus service activation when the activity is installed or removed.

Activities should also NEVER store local state or preferences in the activity bundle itself. These should always be stored in an activity-specific directory in the user's sugar profile, available through the SUGAR_PROFILE environment variable.

Python developers can also get the profile folder this way:
import sugar.env
profile_path = sugar.env.get_profile_path()

== Bundle Structure ==

The activity bundle is a directory, with a name ending in ".activity". Each activity bundle must, in a subdirectory called 'activity', contain a file named "activity.info", and following a special format. For example:

Web.activity/
bin/
web-activity
locale/
de_DE/
activity.linfo
zh_CN/
activity.linfo
activity/
activity.info
activity-web.svg
contents
contents.sig
mimetypes.xml
icons/

; activity
All metadata about the activity is organized in this subdirectory. The <code>contents</code> and <code>contents.sig</code> are manifest and credential files for the entire bundle contents (excepting the <code>contents</code> and <code>contents.sig</code> files themselves), as described by the [[Manifest Specification]]. The optional <code>mimetypes.xml</code> file is a [http://freedesktop.org/wiki/Specifications/shared-mime-info-spec freedesktop.org MIME type file] describing how to recognize the MIME types defined by the activity.

; icons
Contains the icons used by the activity. When using the sugar.activity python package the path is automatically added to the default [http://www.pygtk.org/docs/pygtk/class-gtkicontheme.html gtk icon theme].

== .info File Format ==

.info files follow a key/value pair format, similar to the [http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec fd.o desktop entry spec], but not conforming to it. An example is shown here:

[Activity]
name = Web
activity_version = 1
host_version = 1
bundle_id = com.redhat.Sugar.BrowserActivity
icon = activity-web
exec = sugar-activity browseractivity.BrowserActivity -s
mime_types = application/pdf;image/tiff

A more detailed explanation of the valid properties follows:

[Activity]
: The activity.info file must begin with [Activity], and only that, on the first line of the file

name = Web
: This is the name is displayed in Sugar referring to the activity. A 'name' key without a bracketed language code is the "en_US" localized name of the activity. The activity.info file must have this key.

activity_version = 1
: Each activity.info file must have a "activity_version" key. The version is a single positive integer. Larger versions are considered "newer". The value assigned to this key should be considered '''opaque''' to the activity; the only requirement of the activity is that it must be larger for new activity builds.

host_version = 1
: Each activity.info file must have a "host_version" key. The version is a single positive integer. This specifies the version of the Sugar environment which the activity is compatible with. (fixme: need to specify sugar versions somewhere. Obviously we start with 1.)

bundle_id = com.redhat.Sugar.BrowserActivity
: This is the activity bundle identifier. It is required. It is also used as the activity's default service type when the activity is shared on the network. To determine this type, the distince parts (separated by the '.' character) are reversed, any '.' is replaced by a '_' character, and the type is prefixed by a '_' character. So in this example, the default service type would be "_BrowserActivity_Sugar_redhat_com".

icon = activity-web
: It points to the activity's icon. The icon is looked up in the activity bundle's base directory. It cannot contain a path. When searching for the icon in the activity bundle's base directory, only an file with the icon name and the extension '.svg' will be looked for.

exec = sugar-activity webactivity.WebActivity
: The exec key specifies the executable which [[Sugar]] runs to start the activity instances. Environment variables given on the exec line are expanded. Executable files should be placed into the bin/ directory in the bundle. It should support the following arguments:

; -b, --bundle-id : Identifier of the activity bundle
; -a, --activity-id : Identifier of the activity instance.
; -o, --object-id : Identifier of the associated datastore object.
; -u, --uri : URI to load.

Python activities should generally use the generic sugar-activity executable. Other activities need to adhere to the [[Low-level Activity API]].

mime_types = application/pdf;image/tiff
: List of mime types supported by the activity, separated by semi colons. It's used when opening a file from the web or to present to the user a list of activities which can open a certain journal object.

show_launcher = yes
: This key is optional. If not present, or if present with a value of "yes", the activity is shown with its icon in the [[Sugar]] panel launcher and a valid 'icon' key/value pair is required. If specified with a value of "no", the activity is not shown in the [[Sugar]] panel launcher, and the 'icon' key is not required.

== Activity Name Localization/Translation ==

Localized data lives in the locale directory. Each language stores its localized keys in a separate directory named for the language's ISO code. Localized keys from the 'activity.info' file are stored in the 'activity.linfo' files in that directory. For example, German-localized German (as opposed to Swiss-localized German) language translations are stored in the 'de_DE/activity.linfo' file:

Example.activity/
exampleactivity.py
activity/
activity.info
locale/
de_DE/
activity.linfo
de_CH/
activity.linfo

At this time, only translations for the 'name' key from the 'activity.info' file is supported. A localized 'de_DE/activity.linfo' file would look like:

[Activity]
name = Web

Keys in the languague-specific '.linfo' files selectively override keys from the 'activity.info' file; if a key is not present in the '.linfo' file the value from the 'activity.info' file is used instead.

== Package ==

Activity bundles should be packaged as zip files with the ".xo" extension.

== Other Technologies Comparison ==

Activity bundles are similar to OS X bundles or [[Java JAR files]]; a simple mechanism to encapsulate everything you need in a single directory that can be moved around independently.

It differs from autopackage, it's not a package management system. There's no central database, no scripts get run on install/uninstall. There also is no special file format.

As compared to klik, it's not intended to replicate a local Unix directory structure inside the package; the activity can still link to system
provided binaries and such. There's also no server-side component other than compressing the archive and sending it over the network.There is also no dependency checking since activities are required to be self-contained.

[[Category:API]]
[[Category:Sugar]]
[[Category:Developers]]
[[Category:Software development]]
[[Category:File formats]]

Development Team/Environment

2007-10-30T13:07:21Z

Edsiper: /* Developer Environment */

== Developer Environment ==

Currently we are going to replace the current developer console with a new developer environment, composed by:

'''Analyze Activity''' 
An activity that get useful resources information as: memory usage by activities running, X Server mapped pixmaps, Network interfaces traffic, presence service, etc 
URL: [http://dev.laptop.org/git?p=projects/analyze-activity http://dev.laptop.org/git?p=projects/analyze-activity]

'''Terminal Activity''' 
A Terminal-Shell activity, where the developer or kid can use the Linux shell 
URL: [http://dev.laptop.org/git?p=projects/terminal-activity http://dev.laptop.org/git?p=projects/terminal-activity]

'''Log Activity''' 
Allow to see the activities log files and system logs as /var/log/messages. It will allow to send reports about a given activity or general system to a central server as reports. 
URL: [http://dev.laptop.org/git?p=projects/log-activity http://dev.laptop.org/git?p=projects/log-activity]

Development Team/Environment

2007-10-24T13:32:19Z

Edsiper: /* Developer Environment */

== Developer Environment ==

Currently we are going to replace the current developer console with a new developer environment, composed by:

'''Analyze Activity''' 
An activity that get useful resources information as: memory usage by activities running, X Server mapped pixmaps, Network interfaces traffic, etc 
URL: [http://http://dev.laptop.org/git?p=projects/analyze-activity http://dev.laptop.org/git?p=projects/analyze-activity]

'''Terminal Activity''' 
A Terminal-Shell activity, where the developer or kid can use the Linux shell 
URL: [http://http://dev.laptop.org/git?p=projects/terminal-activity http://dev.laptop.org/git?p=projects/terminal-activity]

'''Log Activity''' 
Allow to see the activities log files, some system log as /var/log/messages and the presence service information. 
URL: [http://http://dev.laptop.org/git?p=projects/log-activity http://dev.laptop.org/git?p=projects/log-activity]

Development Team/Environment

2007-10-24T13:28:35Z

Edsiper: /* Developer Environment */

== Developer Environment ==

Currently we are going to replace the current developer console with a new developer environment, composed by:

'''Analyze Activity''' 
An activity that get useful resources information as: memory usage by activities running, X Server mapped pixmaps, Network interfaces traffic, etc 
URL: [http://http://dev.laptop.org/git?p=projects/analyze-activity http://dev.laptop.org/git?p=projects/analyze-activity]

'''Terminal Activity''' 
A Terminal-Shell activity, where the developer or kid can use the Linux shell 
URL: [http://http://dev.laptop.org/git?p=projects/terminal-activity http://dev.laptop.org/git?p=projects/terminal-activity]

'''Log Activity''' 
Allow to see the activities log files, some system log as /var/log/messages and the presence service information.

Development Team/Environment

2007-10-24T13:24:40Z

Edsiper: /* Developer Environment */

Development Team/Environment

2007-10-24T13:22:16Z

Edsiper: New page: == Developer Environment == Currently we are going to replace the current developer console with a new developer environment, composed by: '''Analyze Activity''' An activity that get...