<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.sugarlabs.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Homunq</id>
	<title>Sugar Labs - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.sugarlabs.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Homunq"/>
	<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/go/Special:Contributions/Homunq"/>
	<updated>2026-06-10T13:22:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Groupthink&amp;diff=37132</id>
		<title>Groupthink</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Groupthink&amp;diff=37132"/>
		<updated>2009-09-11T16:58:23Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;NOTE: this application was never processed because it was not submitted to Google OR included in the relevant category (Category:2009 GSoC applications) at the time.&lt;br /&gt;
&lt;br /&gt;
{{TOCright}}&lt;br /&gt;
====About you====&lt;br /&gt;
&lt;br /&gt;
# Jason Rock&lt;br /&gt;
# rockj (at) rpi (dot) edu&lt;br /&gt;
# [[User:Jrock]]&lt;br /&gt;
# Jrock08&lt;br /&gt;
# English&lt;br /&gt;
# US Central Time Zone&lt;br /&gt;
# [[olpc:Time]] [[Math4Team]], current project multiply at [http://git.sugarlabs.org/projects/multiply].  &lt;br /&gt;
I want to work in open source because I have used open source for a while, but I didn&#039;t feel I had the skills and I didn&#039;t make the time to contribute.  I feel that I have increased my programing and computer science skills to the point where I can work on a real project.  &lt;br /&gt;
I want to contribute to Sugar because I would have loved to have a computer with games and learning tools for me when I was growing up.  I also really enjoy thinking about education.  I always wondered why our education system for the elementary grades didn&#039;t make learning as fun as I feel it could have been.&lt;br /&gt;
&lt;br /&gt;
====About your project====&lt;br /&gt;
&lt;br /&gt;
# Groupthink&lt;br /&gt;
# Groupthink is a development toolkit meant to make collaboration projects easier by abstracting the many algorithms such as failure recovery that are required to effectively collaborate between XO&#039;s.  As a first step, I am looking at incorporating the string tree that allows for lossless merging which is already in the git repo into the project and then patching the write activity to use Groupthink.  I am doing this to help other developers who have applications that could be networked &lt;br /&gt;
&lt;br /&gt;
# I will have to talk more with Ben Schwartz to get a better idea of a potential timeline&lt;br /&gt;
# I feel I will be able to successfully help develop the groupthink toolkit because I am a strong algorithm programmer having competed in many contests at USACO, ACSL, and Topcoder with some success.  I feel that I have a fairly strong base in algorithms from my competitions and formal classes, and am currently taking a theoretical algorithms course that has helped ground my applied algorithms knowledge.  As a young programmer I obviously don&#039;t have a large portfolio, but I have written a neural network, A*, and numerous other algorithms and data structures from scratch.  I have also helped write a simulation of a house fire (in 72 hours for a math modeling competition) and image manipulation with the end goal to solve CAPTCHAs.&lt;br /&gt;
&lt;br /&gt;
====You and the community====&lt;br /&gt;
&lt;br /&gt;
# 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.&lt;br /&gt;
# I would like to see the community group set up in the Aurora Illinois area near the Illinois Math and Science Academy. It would be close enough for me (1 hour drive) and would help out the IMSA OLPC chapter by giving them a lasting resource.&lt;br /&gt;
# If I get stuck I will attempt to find a relevant answer from Google or IRC if it is an implementation problem.  If it is a theoretical problem my two roommates from IMSA are always willing to talk with me about algorithms, and if they aren&#039;t available I will make some new friends on IRC.&lt;br /&gt;
# To keep the community informed I will be active in the IRC channel as well as on the mailing list.  I will also keep an up to date wiki page.&lt;br /&gt;
&lt;br /&gt;
====Miscellaneous====&lt;br /&gt;
[[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&#039;s email address in place of the word &amp;quot;Restart&amp;quot; - your screenshot should contain your email instead.]]&lt;br /&gt;
# 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 &amp;quot;Restart.&amp;quot; See the image on the right for an example. It&#039;s normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.&lt;br /&gt;
# Medium&lt;br /&gt;
# Describe a great learning experience you had as a child.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Category:2009 GSoC applications]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
[[Category:Collaboration]] [[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/results&amp;diff=37131</id>
		<title>Version support for datastore/results</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/results&amp;diff=37131"/>
		<updated>2009-09-11T16:43:42Z</updated>

		<summary type="html">&lt;p&gt;Homunq: Redirected page to Version support for datastore/Results&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Version support for datastore/Results]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/results&amp;diff=37130</id>
		<title>Version support for datastore/results</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/results&amp;diff=37130"/>
		<updated>2009-09-11T16:43:12Z</updated>

		<summary type="html">&lt;p&gt;Homunq: moved Version support for datastore/results to User:Homunq/sandbox&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[User:Homunq/sandbox]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37129</id>
		<title>User:Homunq/sandbox</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37129"/>
		<updated>2009-09-11T16:43:12Z</updated>

		<summary type="html">&lt;p&gt;Homunq: moved Version support for datastore/results to User:Homunq/sandbox&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37128</id>
		<title>User:Homunq/sandbox</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37128"/>
		<updated>2009-09-11T16:42:04Z</updated>

		<summary type="html">&lt;p&gt;Homunq: clearing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/Results&amp;diff=37127</id>
		<title>Version support for datastore/Results</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Version_support_for_datastore/Results&amp;diff=37127"/>
		<updated>2009-09-11T16:41:32Z</updated>

		<summary type="html">&lt;p&gt;Homunq: format for transclusion&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Version support for Datastore ===&lt;br /&gt;
&lt;br /&gt;
Overall I think the project was a success. For various reasons it didn&#039;t quite go the way i imagined, but nevertheless got a fully working prototype I can base further development on. Many of my not directly version related patches were merged upstream for 0.86.&lt;br /&gt;
&lt;br /&gt;
====VCS benchmark ====&lt;br /&gt;
&lt;br /&gt;
My [http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline/trees/master/benchmarks VCS benchmark] that was geared towards the data store use case [[Version support for datastore/Progress#Benchmark_results_2|has shown]] there&#039;s no perfect match -- depending on the hardware Sugar is running on (CPU speed, IO bandwidth, storage size) different VCSs will perform best. This emphasizes the need for a modular design with runtime-selectable VCS backends in case we&#039;re going to use one at all.&lt;br /&gt;
&lt;br /&gt;
==== Datastore redesign proposal ====&lt;br /&gt;
&lt;br /&gt;
The [[Development Team/Datastore Rewrite|current datastore]] codebase doesn&#039;t lend itself very well for adding VCS backend support to it; also the current API (including the names of special properties like &amp;lt;code&amp;gt;uid&amp;lt;/code&amp;gt; for the object identifier) has historically grown and isn&#039;t well-defined in some aspects. My [http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline/blobs/master/datastore-redesign.html proposal] (follow &amp;quot;raw blob data&amp;quot; link) shows how a future datastore implementation could work, including a new API (that&#039;s based on the old one, but with clear definitions and guarantees).&lt;br /&gt;
&lt;br /&gt;
==== Prototype ====&lt;br /&gt;
&lt;br /&gt;
[[Image:journal-version-mockup-2.png|800px|thumb|left|Journal details view with version support]]&lt;br /&gt;
&lt;br /&gt;
The [[Development Team/Datastore Rewrite|current datastore]] has been enhanced to add version support - now based on the new API defined in the proposal mentioned above. The UI side has been adjusted to that new API. To the user, it it totally unobtrusive: the text field showing the time of the last modification just got replaced with a combo box showing all existing versions (with the latest one being the default). Selecting a different version will show the details for that version and also allows the user to resume it. While the UI changes are minimal, the impact is large: even after doing any number of modifications the user can &amp;quot;go back&amp;quot; and look at or even continue working on older versions -- similar to undo / redo functionality some applications offer (though most of them can&#039;t undo anything once the application has been closed).&lt;br /&gt;
&lt;br /&gt;
==== Prefix search support ====&lt;br /&gt;
&lt;br /&gt;
As a test balloon for the [[Development Team/Code Review|code review]] process I added support for doing [http://dev.sugarlabs.org/ticket/1090 full-text searches on specific properties by using prefixes] inside the query string: E.g. entering &amp;quot;mime_type:text/plain&amp;quot; in the Journal query field will only show those entries that have the &amp;quot;mime_type&amp;quot; property set to &amp;quot;text/plain&amp;quot;. Previously the user could only search &#039;&#039;&#039;all&#039;&#039;&#039; properties for &amp;quot;text/plain&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==== Test suite ====&lt;br /&gt;
&lt;br /&gt;
The [http://git.sugarlabs.org/projects/sugar-datastore/repos/versionsupport/trees/onlytest2/ test suite] for sugar-datastore has been revived from an old git version and modified to test the public (=DBus) API instead of the internal ones. It already helped discovering two bugs in my prefix search support changes.&lt;br /&gt;
&lt;br /&gt;
==== Minor bug fixes ====&lt;br /&gt;
&lt;br /&gt;
Several pre-existing bugs have been discovered and fixed in all of sugar-toolkit, sugar-datastore and sugar: [http://dev.sugarlabs.org/ticket/1040 #1040], [http://dev.sugarlabs.org/ticket/1042 #1024], [http://dev.sugarlabs.org/ticket/1053 #1053], [http://dev.sugarlabs.org/ticket/1059 #1059]&lt;br /&gt;
&lt;br /&gt;
==== Minor enhancements ====&lt;br /&gt;
&lt;br /&gt;
A [http://dev.sugarlabs.org/ticket/1089 trace decorator] has been added in order to ease debugging. It helped a lot during version support development. Not having the [http://dev.sugarlabs.org/ticket/1207 layoutmanager side-stepped] by several parts of the data store helped made the prototype code much cleaner. Patches to clean up quite a bit of redundancy in accessing the data store from sugar ([http://dev.sugarlabs.org/ticket/1198 #1198]+[http://dev.sugarlabs.org/ticket/1201 #1201]) and sugar-toolkit ([http://dev.sugarlabs.org/ticket/1197 #1197]) have not been accepted for 0.86.&lt;br /&gt;
&lt;br /&gt;
Unrelated to my version support work, but operating on the same set of modules is a patch to [http://dev.sugarlabs.org/ticket/1215 add a technical details view] (file size, MIME type, creation date) to the Journal details view.&lt;br /&gt;
&lt;br /&gt;
==== Style fixes ====&lt;br /&gt;
&lt;br /&gt;
The [[Development Team/Code Review|code review]] process mandated some stylistic conventions that were not yet followed by some of the pre-existing code. I&#039;ve submitted patches to fix that ([http://dev.sugarlabs.org/ticket/1108 #1108], [http://dev.sugarlabs.org/ticket/1109 #1109]). Also letting the logging code do the formatting of the log message ([http://dev.sugarlabs.org/ticket/1210 #1210], [http://dev.sugarlabs.org/ticket/1211 #1211], [http://dev.sugarlabs.org/ticket/1213 #1213]) has been added to the [[Development Team/Code guidelines#Miscellaneous|style guide]].&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=37126</id>
		<title>Summer of Code</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=37126"/>
		<updated>2009-09-11T16:40:11Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;{{GoogleTrans-en}}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}&amp;lt;/noinclude&amp;gt;{{TOCright}}&lt;br /&gt;
&lt;br /&gt;
From the 2009 FAQ: &amp;quot;Google Summer of Code (GSoC) is a global program that offers student developers stipends to write code for various open source projects.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Sugar Labs Google SoC page: http://socghop.appspot.com/org/show/google/gsoc2009/sugarlabs&lt;br /&gt;
&lt;br /&gt;
This is a project under [[Development Team]]. Jameson Chema Quinn coordinated the 2009 projects and can be contacted with any questions at jameson.quinn -AT- gmail.com.&lt;br /&gt;
&lt;br /&gt;
== 2009 results ==&lt;br /&gt;
&lt;br /&gt;
We had a great year. All 5 of our students were successful, and several of them made really important improvements to Sugar. Here&#039;s the results:&lt;br /&gt;
&lt;br /&gt;
{{:Version_support_for_datastore/Results}}&lt;br /&gt;
&lt;br /&gt;
=== Karma ===&lt;br /&gt;
&lt;br /&gt;
The [[Karma]] GSoC project has been a success. Participant Felipe Lopez Toledo set out to create a high-level library for creating interactive digital learning lessons using only openweb technologies. The result is the [http://git.sugarlabs.org/projects/karma/repos/mainline/blobs/master/js/jquery.karma-0.3.js karma jQuery plugin] that provides high-level functions for manipulating image, audio, and internationalization.&lt;br /&gt;
&lt;br /&gt;
The Karma Project is an initiative to create a platform that enables web developers to create compelling interactive learning materials for the Sugar Learning Environment without having to learn a new set of programming tools.&lt;br /&gt;
&lt;br /&gt;
You can view the first example of lesson [http://karma.sugarlabs.org/karma/examples/adding_up_to_10/index.html &amp;quot;Adding up to 10&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The student, Felipe Lopez Toledo, wrote:&lt;br /&gt;
&lt;br /&gt;
# Simplified functions for:&lt;br /&gt;
#* Drawing using the new canvas API for html5&lt;br /&gt;
#* Adding images dynamically to the canvas API and manipulating them&lt;br /&gt;
#* Playing audio &lt;br /&gt;
# Methods for loading in localized images and audio&lt;br /&gt;
# Mechanism for loading in translated text from a .po file&lt;br /&gt;
# Documentation of the Karma API (need link)&lt;br /&gt;
&lt;br /&gt;
Thanks to the support of Google and Sugar Labs, Karma can now be used to create interactive activities for the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
=== Groupthink ===&lt;br /&gt;
The [[Summer_of_Code/2009/Groupthink|Groupthink GSoC Project]] successfully achieved its specified goals.  The student, Benjamin Schwartz, wrote&lt;br /&gt;
# a [http://bemasc.net/~bens/groupthink/groupthink.gtk_tools.SharedTextView-class.html gtk SharedTextView widget] that provides live shared editing in a self-contained object&lt;br /&gt;
# a [http://bemasc.net/~bens/groupthink/groupthink.groupthink_base.UnorderedString-class.html network interface] to allow sharing this widget over the network&lt;br /&gt;
# a SharedTextDemo activity (versions [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/014795.html 1], [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/015346.html 2], [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/015713.html 3], [http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016739.html 4], and [http://lists.sugarlabs.org/archive/sugar-devel/2009-July/017004.html 5]) to demonstrate the use of this widget&lt;br /&gt;
# an automated [http://bemasc.net/~bens/groupthink/groupthink.groupthink_base.Group-class.html#dumps serialization system] for saving and loading state [http://bemasc.net/~bens/groupthink/groupthink.sugar_tools.GroupActivity-class.html#read_file with the Journal]&lt;br /&gt;
# [http://bemasc.net/~bens/groupthink/groupthink.sugar_tools.GroupActivity-class.html other] code necessary so that Sugar activities could seamlessly rejoin a shared instance and merge in changes made offline&lt;br /&gt;
# [http://git.sugarlabs.org/projects/pippy/repos/pippy-groupthink/commits/0f30ab2a17670d3f7e7723fe4f4756333030c3e0 patches] to enable live shared editing of Python code, with syntax highlighting and Undo/Redo, in [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4041#version-35 Pippy-35]&lt;br /&gt;
# extensive [http://bemasc.net/~bens/groupthink/ API documentation] for Groupthink.&lt;br /&gt;
&lt;br /&gt;
Thanks to the support from Sugar Labs and Google, Groupthink has grown from a toy project into a library that developers can really use.&lt;br /&gt;
&lt;br /&gt;
== Previous Introduction ==&lt;br /&gt;
&lt;br /&gt;
The purpose of this page (was) to coordinate a Sugar Labs Summer of Code effort.&lt;br /&gt;
&lt;br /&gt;
=== What (made) a good project ===&lt;br /&gt;
&lt;br /&gt;
Our focus is on &#039;&#039;&#039;collaboration&#039;&#039;&#039; and &#039;&#039;&#039;community&#039;&#039;&#039; for the summer 2009 round of projects, though we&#039;ll also consider thoughtful proposals that lie outside these two areas and can make a strong case for how they would support the Sugar Labs [[Sugar_Labs|mission]]. &lt;br /&gt;
&lt;br /&gt;
==== Collaboration ====&lt;br /&gt;
&lt;br /&gt;
This refers to API or activity work that makes [[olpc:Activity_sharing | collaboration]] &amp;quot;work better.&amp;quot; A good metric for &amp;quot;works better&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to have caused the highest increase in children-hours spent collaborating over Sugar Activities?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== Community ====&lt;br /&gt;
&lt;br /&gt;
This refers to meta-work that makes it easy for Sugar to reach a broader [[Sugar Labs]]; this includes development tools (and accompanying implementation of processes and training), internationalization/localization, accessibility, infrastructure-building, and porting Sugar to other platforms. &lt;br /&gt;
&lt;br /&gt;
A good metric for &amp;quot;reaches a broader community&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to cause the highest increase in SL community members that have participated consistently on a team for a minimum of 3 months?&amp;quot;&lt;br /&gt;
{{:Summer of Code/Getting Involved}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&lt;br /&gt;
==Subpages==&lt;br /&gt;
{{Special:PrefixIndex/{{PAGENAMEE}}/}}&lt;br /&gt;
[[Category:Project]]&lt;br /&gt;
[[Category:Participate]]&lt;br /&gt;
[[Category:GSoC]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37017</id>
		<title>User:Homunq/sandbox</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=User:Homunq/sandbox&amp;diff=37017"/>
		<updated>2009-09-09T16:10:42Z</updated>

		<summary type="html">&lt;p&gt;Homunq: Created page with &amp;#039;Sascha, please fill in here.&amp;#039;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sascha, please fill in here.&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=37016</id>
		<title>Summer of Code</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=37016"/>
		<updated>2009-09-09T16:10:02Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;{{GoogleTrans-en}}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}&amp;lt;/noinclude&amp;gt;{{TOCright}}&lt;br /&gt;
&lt;br /&gt;
{{Draft}}&lt;br /&gt;
&lt;br /&gt;
From the 2009 FAQ: &amp;quot;Google Summer of Code (GSoC) is a global program that offers student developers stipends to write code for various open source projects.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Sugar Labs Google SoC page: http://socghop.appspot.com/org/show/google/gsoc2009/sugarlabs&lt;br /&gt;
&lt;br /&gt;
This is a project under [[Development Team]]. [[User:Mchua|Mchua]] is the current project coordinator and can be contacted with any questions.&lt;br /&gt;
&lt;br /&gt;
== 2009 results ==&lt;br /&gt;
&lt;br /&gt;
We had a great year. All 5 of our students were successful, and several of them made really important improvements to Sugar. Here&#039;s the results:&lt;br /&gt;
&lt;br /&gt;
{{:Version_support_for_datastore/results}}&lt;br /&gt;
&lt;br /&gt;
=== Karma ===&lt;br /&gt;
&lt;br /&gt;
The [[Karma]] GSoC project has been a success. Participant Felipe Lopez Toledo set out to create a high-level library for creating interactive digital learning lessons using only openweb technologies. The result is the [http://git.sugarlabs.org/projects/karma/repos/mainline/blobs/master/js/jquery.karma-0.3.js karma jQuery plugin] that provides high-level functions for manipulating image, audio, and internationalization.&lt;br /&gt;
&lt;br /&gt;
The Karma Project is an initiative to create a platform that enables web developers to create compelling interactive learning materials for the Sugar Learning Environment without having to learn a new set of programming tools.&lt;br /&gt;
&lt;br /&gt;
You can view the first example of lesson [http://karma.sugarlabs.org/karma/examples/adding_up_to_10/index.html &amp;quot;Adding up to 10&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The student, Felipe Lopez Toledo, wrote:&lt;br /&gt;
&lt;br /&gt;
# Simplified functions for:&lt;br /&gt;
#* Drawing using the new canvas API for html5&lt;br /&gt;
#* Adding images dynamically to the canvas API and manipulating them&lt;br /&gt;
#* Playing audio &lt;br /&gt;
# Methods for loading in localized images and audio&lt;br /&gt;
# Mechanism for loading in translated text from a .po file&lt;br /&gt;
# Documentation of the Karma API (need link)&lt;br /&gt;
&lt;br /&gt;
Thanks to the support of Google and SugarLabs, Karma can now be used to create interactive activities for the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
=== Groupthink ===&lt;br /&gt;
The [[Summer_of_Code/2009/Groupthink|Groupthink GSoC Project]] successfully achieved its specified goals.  The student, Benjamin Schwartz, wrote&lt;br /&gt;
# a [http://bemasc.net/~bens/groupthink/groupthink.gtk_tools.SharedTextView-class.html gtk SharedTextView widget] that provides live shared editing in a self-contained object&lt;br /&gt;
# a [http://bemasc.net/~bens/groupthink/groupthink.groupthink_base.UnorderedString-class.html network interface] to allow sharing this widget over the network&lt;br /&gt;
# a SharedTextDemo activity (versions [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/014795.html 1], [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/015346.html 2], [http://lists.sugarlabs.org/archive/sugar-devel/2009-June/015713.html 3], [http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016739.html 4], and [http://lists.sugarlabs.org/archive/sugar-devel/2009-July/017004.html 5]) to demonstrate the use of this widget&lt;br /&gt;
# an automated [http://bemasc.net/~bens/groupthink/groupthink.groupthink_base.Group-class.html#dumps serialization system] for saving and loading state [http://bemasc.net/~bens/groupthink/groupthink.sugar_tools.GroupActivity-class.html#read_file with the Journal]&lt;br /&gt;
# [http://bemasc.net/~bens/groupthink/groupthink.sugar_tools.GroupActivity-class.html other] code necessary so that Sugar activities could seamlessly rejoin a shared instance and merge in changes made offline&lt;br /&gt;
# [http://git.sugarlabs.org/projects/pippy/repos/pippy-groupthink/commits/0f30ab2a17670d3f7e7723fe4f4756333030c3e0 patches] to enable live shared editing of Python code, with syntax highlighting and Undo/Redo, in [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4041#version-35 Pippy-35]&lt;br /&gt;
# extensive [http://bemasc.net/~bens/groupthink/ API documentation] for Groupthink.&lt;br /&gt;
&lt;br /&gt;
Thanks to the support from Sugar Labs and Google, Groupthink has grown from a toy project into a library that developers can really use.&lt;br /&gt;
&lt;br /&gt;
== Previous Introduction ==&lt;br /&gt;
&lt;br /&gt;
The purpose of this page (was) to coordinate a Sugar Labs Summer of Code effort.&lt;br /&gt;
&lt;br /&gt;
=== What (made) a good project ===&lt;br /&gt;
&lt;br /&gt;
Our focus is on &#039;&#039;&#039;collaboration&#039;&#039;&#039; and &#039;&#039;&#039;community&#039;&#039;&#039; for the summer 2009 round of projects, though we&#039;ll also consider thoughtful proposals that lie outside these two areas and can make a strong case for how they would support the Sugar Labs [[Sugar_Labs|mission]]. &lt;br /&gt;
&lt;br /&gt;
==== Collaboration ====&lt;br /&gt;
&lt;br /&gt;
This refers to API or activity work that makes [[olpc:Activity_sharing | collaboration]] &amp;quot;work better.&amp;quot; A good metric for &amp;quot;works better&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to have caused the highest increase in children-hours spent collaborating over Sugar Activities?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== Community ====&lt;br /&gt;
&lt;br /&gt;
This refers to meta-work that makes it easy for Sugar to reach a broader [[Sugar Labs]]; this includes development tools (and accompanying implementation of processes and training), internationalization/localization, accessibility, infrastructure-building, and porting Sugar to other platforms. &lt;br /&gt;
&lt;br /&gt;
A good metric for &amp;quot;reaches a broader community&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to cause the highest increase in SL community members that have participated consistently on a team for a minimum of 3 months?&amp;quot;&lt;br /&gt;
{{:Summer of Code/Getting Involved}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&lt;br /&gt;
==Subpages==&lt;br /&gt;
{{Special:PrefixIndex/{{PAGENAMEE}}/}}&lt;br /&gt;
[[Category:Project]]&lt;br /&gt;
[[Category:Participate]]&lt;br /&gt;
[[Category:GSoC]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=35663</id>
		<title>Summer of Code</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code&amp;diff=35663"/>
		<updated>2009-08-24T09:05:35Z</updated>

		<summary type="html">&lt;p&gt;Homunq: 2009 results&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}&amp;lt;/noinclude&amp;gt;{{TOCright}}&lt;br /&gt;
&lt;br /&gt;
{{Draft}}&lt;br /&gt;
&lt;br /&gt;
From the 2009 FAQ: &amp;quot;Google Summer of Code (GSoC) is a global program that offers student developers stipends to write code for various open source projects.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Sugar Labs Google SoC page: http://socghop.appspot.com/org/show/google/gsoc2009/sugarlabs&lt;br /&gt;
&lt;br /&gt;
This is a project under [[Development Team]]. [[User:Mchua|Mchua]] is the current project coordinator and can be contacted with any questions.&lt;br /&gt;
&lt;br /&gt;
== 2009 results ==&lt;br /&gt;
&lt;br /&gt;
We had a great year. All 5 of our students were successful, and several of them made really important improvements to Sugar. Here&#039;s the results:&lt;br /&gt;
&lt;br /&gt;
{{Version_support_for_datastore/results}}&lt;br /&gt;
&lt;br /&gt;
(other projects: you can add your summary here, or, preferably, transclude as I have done above.)&lt;br /&gt;
&lt;br /&gt;
== Previous Introduction ==&lt;br /&gt;
&lt;br /&gt;
The purpose of this page (was) to coordinate a Sugar Labs Summer of Code effort.&lt;br /&gt;
&lt;br /&gt;
=== What (made) a good project ===&lt;br /&gt;
&lt;br /&gt;
Our focus is on &#039;&#039;&#039;collaboration&#039;&#039;&#039; and &#039;&#039;&#039;community&#039;&#039;&#039; for the summer 2009 round of projects, though we&#039;ll also consider thoughtful proposals that lie outside these two areas and can make a strong case for how they would support the Sugar Labs [[Sugar_Labs|mission]]. &lt;br /&gt;
&lt;br /&gt;
==== Collaboration ====&lt;br /&gt;
&lt;br /&gt;
This refers to API or activity work that makes [[olpc:Activity_sharing | collaboration]] &amp;quot;work better.&amp;quot; A good metric for &amp;quot;works better&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to have caused the highest increase in children-hours spent collaborating over Sugar Activities?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== Community ====&lt;br /&gt;
&lt;br /&gt;
This refers to meta-work that makes it easy for Sugar to reach a broader [[Sugar Labs]]; this includes development tools (and accompanying implementation of processes and training), internationalization/localization, accessibility, infrastructure-building, and porting Sugar to other platforms. &lt;br /&gt;
&lt;br /&gt;
A good metric for &amp;quot;reaches a broader community&amp;quot; is to ask the following: &amp;quot;6 months after the summer ends, which projects are likely to cause the highest increase in SL community members that have participated consistently on a team for a minimum of 3 months?&amp;quot;&lt;br /&gt;
{{:Summer of Code/Getting Involved}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&lt;br /&gt;
==Subpages==&lt;br /&gt;
{{Special:PrefixIndex/{{PAGENAMEE}}/}}&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Participate]]&lt;br /&gt;
[[Category:Project]]&lt;br /&gt;
[[Category:GSoC]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30809</id>
		<title>File:Grabsuggieglidie-2.svg</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30809"/>
		<updated>2009-06-20T20:08:42Z</updated>

		<summary type="html">&lt;p&gt;Homunq: uploaded a new version of &amp;quot;File:Grabsuggieglidie-2.svg&amp;quot;:&amp;amp;#32;fixed wonky line (worked in inkscape but not here???)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;loosely inspired by http://www.sugarglidertips.com/wp-content/uploads/2009/02/sugar-glider-00191.jpg&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30803</id>
		<title>File:Grabsuggieglidie-2.svg</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30803"/>
		<updated>2009-06-20T19:03:29Z</updated>

		<summary type="html">&lt;p&gt;Homunq: uploaded a new version of &amp;quot;File:Grabsuggieglidie-2.svg&amp;quot;:&amp;amp;#32;another version lightly retouched (smaller body, etc.)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;loosely inspired by http://www.sugarglidertips.com/wp-content/uploads/2009/02/sugar-glider-00191.jpg&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie.svg&amp;diff=30802</id>
		<title>File:Grabsuggieglidie.svg</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie.svg&amp;diff=30802"/>
		<updated>2009-06-20T19:00:10Z</updated>

		<summary type="html">&lt;p&gt;Homunq: another version lightly retouched (smaller body, etc.)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;another version lightly retouched (smaller body, etc.)&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30801</id>
		<title>File:Grabsuggieglidie-2.svg</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Grabsuggieglidie-2.svg&amp;diff=30801"/>
		<updated>2009-06-20T18:07:53Z</updated>

		<summary type="html">&lt;p&gt;Homunq: loosely inspired by http://www.sugarglidertips.com/wp-content/uploads/2009/02/sugar-glider-00191.jpg&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;loosely inspired by http://www.sugarglidertips.com/wp-content/uploads/2009/02/sugar-glider-00191.jpg&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick/Linux&amp;diff=30715</id>
		<title>Sugar on a Stick/Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick/Linux&amp;diff=30715"/>
		<updated>2009-06-19T13:02:27Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOCright}}&lt;br /&gt;
== Introduction ==&lt;br /&gt;
This page helps you to put your [[Sugar on a Stick]] image on a USB flash drive under Linux.    If you have questions, trouble or feedback, please let us know on the [[Talk:Sugar on a Stick|SoaS talk]] page. &amp;quot;Sugar on a Stick&amp;quot; is provided in a number of variants. If you can improve these instructions, please edit the page and do so!&lt;br /&gt;
&lt;br /&gt;
== [[Sugar on a Stick/Installation/OLPC | SoaS on an OLPC XO-1]]==&lt;br /&gt;
* See [[Sugar on a Stick/Installation/OLPC]] for booting an OLPC XO-1 with SoaS images.&lt;br /&gt;
&lt;br /&gt;
== openSUSE instructions ==&lt;br /&gt;
&lt;br /&gt;
For the openSUSE Sugar variant (bundled with 55+ activities) go to http://en.opensuse.org/Sugar&lt;br /&gt;
 also: http://wiki.sugarlabs.org/go/VMware&lt;br /&gt;
&lt;br /&gt;
== Fedora and Ubuntu instructions ==&lt;br /&gt;
&lt;br /&gt;
This is known to work in Fedora and Ubuntu.&lt;br /&gt;
&lt;br /&gt;
First, start downloading the SoaS &amp;lt;tt&amp;gt;.iso&amp;lt;/tt&amp;gt; image from the [[Sugar on a Stick#Downloading alternative images]] table, then return here.&lt;br /&gt;
&lt;br /&gt;
* Make sure you have the &#039;&#039;syslinux&#039;&#039; package installed on the operating system that you will use to prepare the Live USB image. It is recommended that you also have the &#039;&#039;isomd5sum&#039;&#039; package installed. The &#039;&#039;cryptsetup&#039;&#039; package is another option potentially used by the &amp;quot;livecd-iso-to-disk&amp;quot; installation script. (On Ubuntu, &amp;lt;code&amp;gt;sudo apt-get install syslinux isomd5sum cryptsetup&amp;lt;/code&amp;gt; will install the packages.)&lt;br /&gt;
**&#039;&#039;syslinux&#039;&#039; is needed to set up booting on the FAT file system of the USB disc or Live CD.&lt;br /&gt;
**&#039;&#039;isomd5sum&#039;&#039; is needed for the recommended verification step, which checks that the .iso file is complete after its travels. If there is a problem with the .iso file, the script will exit and provide a failure message.  The verification step can be bypassed by using the &amp;lt;code&amp;gt;--noverify&amp;lt;/code&amp;gt; option.&lt;br /&gt;
**&#039;&#039;cryptsetup&#039;&#039; is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the  recommended &amp;lt;code&amp;gt;--unencrypted-home&amp;lt;/code&amp;gt; option. The &amp;lt;code&amp;gt;--unencrypted-home&amp;lt;/code&amp;gt; option is preferred because the reduced overhead improves robustness with the compressed &#039;&#039;squashfs&#039;&#039; file system employed by the Live USB deployment.&lt;br /&gt;
* Plug in a 1GB or larger USB stick into your computer.&lt;br /&gt;
* Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)&lt;br /&gt;
&lt;br /&gt;
* Check the USB device. In the example below the device is /dev/sdb:&lt;br /&gt;
: &amp;lt;tt&amp;gt;&#039;&#039;&#039;df -h&#039;&#039;&#039;&amp;lt;/tt&amp;gt;&lt;br /&gt;
 Filesystem            Size  Used Avail Use% Mounted on&lt;br /&gt;
 /dev/sda1              19G  7.0G   11G  40% /&lt;br /&gt;
 tmpfs                 1.5G     0  1.5G   0% /lib/init/rw&lt;br /&gt;
 varrun                1.5G   96K  1.5G   1% /var/run&lt;br /&gt;
 varlock               1.5G     0  1.5G   0% /var/lock&lt;br /&gt;
 udev                  1.5G  2.9M  1.5G   1% /dev&lt;br /&gt;
 tmpfs                 1.5G  104K  1.5G   1% /dev/shm&lt;br /&gt;
 lrm                   1.5G  2.0M  1.5G   1% /lib/modules/2.6.27-11-generic/volatile&lt;br /&gt;
 /dev/sdb1             996M  913M   84M  92% /mnt/myUSBdisc&lt;br /&gt;
&lt;br /&gt;
* Then check to see that the partition is marked as bootable,&amp;lt;br&amp;gt;&lt;br /&gt;
: &amp;lt;tt&amp;gt;sudo fdisk &#039;&#039;&#039;-l&#039;&#039;&#039;&amp;lt;/tt&amp;gt; &#039;&#039;&amp;lt;----that&#039;s a lowercase letter &#039;L&#039; for the &#039;&#039;&#039;l&#039;&#039;&#039;ist option.&#039;&#039;&lt;br /&gt;
You should see output that looks like this:&lt;br /&gt;
 Disk /dev/sdb: 1047 MB, 1047265280 bytes&lt;br /&gt;
 255 heads, 63 sectors/track, 127 cylinders&lt;br /&gt;
 Units = cylinders of 16065 * 512 = 8225280 bytes&lt;br /&gt;
 Disk identifier: 0x0008325f&lt;br /&gt;
 . &lt;br /&gt;
  Device Boot      Start         End      Blocks   Id  System&lt;br /&gt;
 /dev/sdb1   *           1         127     1020096    6  FAT16&lt;br /&gt;
The &#039;*&#039; under the Boot column is what you want to see.&lt;br /&gt;
: If not, then&lt;br /&gt;
:* For Ubuntu 8.10, menu: System -&amp;gt; Administration -&amp;gt; Partition Editor (GParted).&lt;br /&gt;
::# Select your USB device (/dev/sd&#039;&#039;b&#039;&#039; for the rest of these instructions),&lt;br /&gt;
::# then your partition (/dev/sd&#039;&#039;b1&#039;&#039;),&lt;br /&gt;
::# then menu: Partition -&amp;gt; Manage Flags,&lt;br /&gt;
::# check the boot box,&lt;br /&gt;
::# and Close to mark the partition as bootable.&lt;br /&gt;
&lt;br /&gt;
:* For Fedora,&lt;br /&gt;
::#  &amp;lt;tt&amp;gt;parted /dev/sd&#039;&#039;b&#039;&#039;&amp;lt;/tt&amp;gt;&lt;br /&gt;
::# toggle 1 boot&lt;br /&gt;
::# quit &lt;br /&gt;
&lt;br /&gt;
* Also, check to see that you do not already have an existing bootloader (such as GRUB) in the MBR of your stick. (If you have not previously used this stick as a live boot, you can skip this step.) To be sure that the USB stick&#039;s MBR is wiped clean, overwrite it completely using:&lt;br /&gt;
: &amp;lt;tt&amp;gt;dd if=/dev/zero of=/dev/sd&#039;&#039;b&#039;&#039; bs=446 count=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
** (Actually, that didn&#039;t work for me. But this did:&lt;br /&gt;
**: &amp;lt;tt&amp;gt;lilo -M /dev/sd&#039;&#039;b&#039;&#039;&amp;lt;/tt&amp;gt;&lt;br /&gt;
**:It put in a standard MBR that boots whichever partition has been called bootable. It does not install LILO as such.)&lt;br /&gt;
* Unmount the drive,&amp;lt;br&amp;gt;&lt;br /&gt;
: &amp;lt;tt&amp;gt;sudo umount /dev/sd&#039;&#039;b1&#039;&#039;&amp;lt;/tt&amp;gt;&lt;br /&gt;
* Change mode to make the script executable. &lt;br /&gt;
: &amp;lt;tt&amp;gt;chmod +x livecd-iso-to-disk.sh&amp;lt;/tt&amp;gt;&lt;br /&gt;
* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.&lt;br /&gt;
: &amp;lt;tt&amp;gt;sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sd&#039;&#039;b1&#039;&#039;&amp;lt;/tt&amp;gt;&lt;br /&gt;
The &#039;&#039;livecd-iso-to-disk&#039;&#039; installation has the advantage over the &#039;&#039;liveusb-creator&#039;&#039; installation method by allowing a persistent /home/liveuser folder with the &amp;lt;tt&amp;gt;--home-size-mb &#039;&#039;NNN&#039;&#039;&amp;lt;/tt&amp;gt; option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but &amp;lt;u&amp;gt;leaving out&amp;lt;/u&amp;gt; the --home-size-mb NNN option).&lt;br /&gt;
* The &amp;lt;code&amp;gt;--delete-home&amp;lt;/code&amp;gt; option is used to avoid an error message while requesting both a new home (with &amp;lt;code&amp;gt;--home-size-mb&amp;lt;/code&amp;gt;) and a persistent home (indirectly with &amp;lt;code&amp;gt;--unencrypted-home&amp;lt;/code&amp;gt;). You wouldn&#039;t use the --delete-home option on an upgrade of the operation system only.&lt;br /&gt;
Depending on the size of your USB stick, you may have to decrease &amp;lt;code&amp;gt;--overlay-size-mb&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;--home-size-mb&amp;lt;/code&amp;gt; values (example, for 1 GB stick, use 200 for each).&lt;br /&gt;
* If you get an error about udevinfo, you have the new version of udev where &amp;quot;udevadm info&amp;quot; is the proper command. Create an executable file called udevinfo somewhere in your path with the following contents:&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 udevadm info $*&lt;br /&gt;
&lt;br /&gt;
== What&#039;s next? ==&lt;br /&gt;
&lt;br /&gt;
After you&#039;ve created your stick, it&#039;s time to [[Sugar_on_a_Stick#Boot|boot your stick]] and [[Sugar on a Stick/Getting Involved | test]] it out.  Please also [[Sugar on a Stick/Getting Involved/Testing | report]] your observations.&lt;br /&gt;
&lt;br /&gt;
[[Category:HowTo]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Develop-39.xo&amp;diff=28406</id>
		<title>File:Develop-39.xo</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Develop-39.xo&amp;diff=28406"/>
		<updated>2009-05-02T18:40:54Z</updated>

		<summary type="html">&lt;p&gt;Homunq: uploaded a new version of &amp;quot;Image:Develop-39.xo&amp;quot;: fixed for old/new bundlebuilder&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;for mantaraya testing&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Develop-39.xo&amp;diff=28405</id>
		<title>File:Develop-39.xo</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Develop-39.xo&amp;diff=28405"/>
		<updated>2009-05-02T17:56:12Z</updated>

		<summary type="html">&lt;p&gt;Homunq: for mantaraya testing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;for mantaraya testing&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Keyboard_Action&amp;diff=27999</id>
		<title>Design Team/Proposals/Keyboard Action</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Keyboard_Action&amp;diff=27999"/>
		<updated>2009-04-24T17:02:40Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DesignProposal|subject=Keyboard_Action}}&amp;lt;!-- Keep this line --&amp;gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&amp;lt;!-- START OF BLOCK -- 1. COPY &amp;amp; PASTE this BLOCK to below the END OF BLOCK line.&lt;br /&gt;
                                  2. PASTE it before any pre-existing proposal,&lt;br /&gt;
                                  3. then OVERWRITE the place holders with your information,&lt;br /&gt;
                                  4. and DELETE the START &amp;amp; END OF BLOCK instruction lines.&lt;br /&gt;
                                  5. Click [Show preview] to check formatting, and adjust as necessary.&lt;br /&gt;
                                  6. Click [Save page] to complete the edit.&lt;br /&gt;
                                                                                              --&amp;gt;&lt;br /&gt;
==[&amp;lt;span class=&amp;quot;plainlinks&amp;quot;&amp;gt;[{{fullurle:index.php|title={{PAGENAMEE}}&amp;amp;action=edit}} edit]&amp;lt;/span&amp;gt;] &amp;lt;Your proposal&#039;s pithy name here&amp;gt;==  &amp;lt;!-- Leave the == prefix and suffix ==                                               --&amp;gt;&lt;br /&gt;
:&#039;&#039;&#039;Rationale:&#039;&#039;&#039;                    &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: &amp;lt;Your rationale here&amp;gt;             &amp;lt;!-- leave the :: prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Features:&#039;&#039;&#039;                     &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:# &amp;lt;1st feature here&amp;gt;                &amp;lt;!-- leave the :# prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
:# &amp;lt;2nd feature here&amp;gt;                &amp;lt;!-- ditto --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Implementation Details:&#039;&#039;&#039;       &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: &amp;lt;Details here&amp;gt;                    &amp;lt;!-- leave the :: prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewer Comments:&#039;&#039;&#039;            &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: comments here       &amp;lt;!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~ &lt;br /&gt;
END OF BLOCK line --&amp;gt; &amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pre-existing Proposal Block --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== discoverable, consistent, lazy-programmer keyboard shortcuts ==&lt;br /&gt;
(revised 4/23/09)&lt;br /&gt;
&lt;br /&gt;
monopoly key (windows key) would be the grab key. &lt;br /&gt;
&lt;br /&gt;
Insert would be the frame key (mnemonic: &amp;quot;INSet&amp;quot;). This would also be available as alt-F3 or alt-monopoly as a (hopefully unnecessary) backup.&lt;br /&gt;
&lt;br /&gt;
F1-F4 would be view / zoom level, as currently. Pressing F3 while already in home view would toggle view all/ring view, while pressing F4 while already in app view would cycle through open activities. If we ever get different friend sets or something, we could do something similar for F2. F9-F12 would be reserved for sugar, too - for instance, journal, context-sensitive help. F5-F8 would be for activity-specific functions. (IMO this is consistent with the XO keyboard and a fair way to divvy up this set of keys)&lt;br /&gt;
&lt;br /&gt;
alt-&amp;lt;key&amp;gt; would be reserved for sugar-wide (or nearly) shortcuts. &amp;lt;s&amp;gt;This would preseve z, x, c, v as the 1984 mac standards.&amp;lt;/s&amp;gt; Globally-available keys: print screen, view source, power/volume/brightness controls, shut activity (alt-escape), next/previous activity (alt-tab), possibly in the future chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down alt would bring up a static cheat sheet of these shortcuts after a short delay.&lt;br /&gt;
&lt;br /&gt;
ctrl-&amp;lt;key&amp;gt; would be reserved for application-specific shortcuts, including z, x, c, v. ctrl-&amp;lt;numeral&amp;gt; would switch toolbars to toolbar x. Holding ctrl would immediately bring up a translucent letter over the appropriate icon in the toolbar. Translucent letters would also flash briefly when clicking on a toolbar button, to aid discovery. Python apps (at least) would get keys assigned for free, though they could do it manually with an underscore char before the given letter (&amp;quot;_Print&amp;quot; would be p, &amp;quot;P_rint&amp;quot; would be r, &amp;quot;Print__o&amp;quot; would be o; all would display as simply &amp;quot;Print&amp;quot;). This behind-the-scenes magic would respect localization - shortcuts would change by language. Shortcuts would be available even if the given toolbar were not open. &amp;lt;s&amp;gt;Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.&amp;lt;/s&amp;gt; ctrl-shift would be the reverse action, and ctrl-alt would be modified action (such as paste and pop from clipboard instead of just paste). &lt;br /&gt;
&lt;br /&gt;
Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second. If a global key (such as Insert or F1) was pressed while ctrl was toggled on, it would be sent to the current activity, not caught by Sugar. This would allow legacy applications which needed these keys to function.&lt;br /&gt;
&lt;br /&gt;
All other keys would have their conventional meaning, except for num lock. The number pad would always be numbers, and pressing num lock would cause the machine to make a loud farting noise.&lt;br /&gt;
&lt;br /&gt;
proposal by [[User:Homunq|Homunq]] 21:06, 22 March 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewer Comments:&#039;&#039;&#039;            &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
::http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03332.html&lt;br /&gt;
::[&amp;lt;span class=&amp;quot;plainlinks&amp;quot;&amp;gt;[{{fullurle:index.php|title=Talk:Design_Team/Vision/Proposals/Keyboard_Action&amp;amp;action=edit&amp;amp;section=1}} edit]&amp;lt;/span&amp;gt;] [[Talk:Design_Team/Vision/Proposals/Keyboard_Action#discoverable,_consistent,_lazy-programmer_keyboard_shortcuts | comments on talk page]]&lt;br /&gt;
&lt;br /&gt;
::    &amp;lt;!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Keyboard_Action&amp;diff=27998</id>
		<title>Design Team/Proposals/Keyboard Action</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Keyboard_Action&amp;diff=27998"/>
		<updated>2009-04-24T17:01:32Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DesignProposal|subject=Keyboard_Action}}&amp;lt;!-- Keep this line --&amp;gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&amp;lt;!-- START OF BLOCK -- 1. COPY &amp;amp; PASTE this BLOCK to below the END OF BLOCK line.&lt;br /&gt;
                                  2. PASTE it before any pre-existing proposal,&lt;br /&gt;
                                  3. then OVERWRITE the place holders with your information,&lt;br /&gt;
                                  4. and DELETE the START &amp;amp; END OF BLOCK instruction lines.&lt;br /&gt;
                                  5. Click [Show preview] to check formatting, and adjust as necessary.&lt;br /&gt;
                                  6. Click [Save page] to complete the edit.&lt;br /&gt;
                                                                                              --&amp;gt;&lt;br /&gt;
==[&amp;lt;span class=&amp;quot;plainlinks&amp;quot;&amp;gt;[{{fullurle:index.php|title={{PAGENAMEE}}&amp;amp;action=edit}} edit]&amp;lt;/span&amp;gt;] &amp;lt;Your proposal&#039;s pithy name here&amp;gt;==  &amp;lt;!-- Leave the == prefix and suffix ==                                               --&amp;gt;&lt;br /&gt;
:&#039;&#039;&#039;Rationale:&#039;&#039;&#039;                    &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: &amp;lt;Your rationale here&amp;gt;             &amp;lt;!-- leave the :: prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Features:&#039;&#039;&#039;                     &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:# &amp;lt;1st feature here&amp;gt;                &amp;lt;!-- leave the :# prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
:# &amp;lt;2nd feature here&amp;gt;                &amp;lt;!-- ditto --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Implementation Details:&#039;&#039;&#039;       &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: &amp;lt;Details here&amp;gt;                    &amp;lt;!-- leave the :: prefix, overwrite the rest of this line --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewer Comments:&#039;&#039;&#039;            &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
:: comments here       &amp;lt;!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~ &lt;br /&gt;
END OF BLOCK line --&amp;gt; &amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pre-existing Proposal Block --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== discoverable, consistent, lazy-programmer keyboard shortcuts ==&lt;br /&gt;
(revised 4/23/09)&lt;br /&gt;
&lt;br /&gt;
monopoly key (windows key) would be the grab key. &lt;br /&gt;
&lt;br /&gt;
Insert would be the frame key (mnemonic: &amp;quot;INSet&amp;quot;). This would also be available as alt-F3 or alt-monopoly as a (hopefully unnecessary) backup.&lt;br /&gt;
&lt;br /&gt;
F1-F4 would be view / zoom level, as currently. Pressing F3 while already in home view would toggle view all/ring view, while pressing F4 while already in app view would cycle through open activities. If we ever get different friend sets or something, we could do something similar for F2. F9-F12 would be reserved for sugar, too - for instance, journal, context-sensitive help. F5-F8 would be for activity-specific functions. (IMO this is consistent with the XO keyboard and a fair way to divvy up this set of keys)&lt;br /&gt;
&lt;br /&gt;
alt-&amp;lt;key&amp;gt; would be reserved for sugar-wide (or nearly) shortcuts. &amp;lt;s&amp;gt;This would preseve z, x, c, v as the 1984 mac standards.&amp;lt;/s&amp;gt; Globally-available keys: print screen, view source, power/volume/brightness controls, shut activity (alt-escape), next/previous activity (alt-tab), possibly in the future chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down alt would bring up a static cheat sheet of these shortcuts after a short delay.&lt;br /&gt;
&lt;br /&gt;
ctrl-&amp;lt;key&amp;gt; would be reserved for application-specific shortcuts, including z, x, c, v. ctrl-&amp;lt;numeral&amp;gt; would switch toolbars to toolbar x. Holding ctrl would immediately bring up a translucent letter over the appropriate icon in the toolbar. Translucent letters would also flash briefly when clicking on a toolbar button, to aid discovery. Python apps (at least) would get keys assigned for free, though they could do it manually with an underscore char before the given letter (&amp;quot;_Print&amp;quot; would be p, &amp;quot;P_rint&amp;quot; would be r, &amp;quot;Print__o&amp;quot; would be o). This behind-the-scenes magic would respect localization - shortcuts would change by language. Shortcuts would be available even if the given toolbar were not open. &amp;lt;s&amp;gt;Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.&amp;lt;/s&amp;gt; ctrl-shift would be the reverse action, and ctrl-alt would be modified action (such as paste and pop from clipboard instead of just paste). &lt;br /&gt;
&lt;br /&gt;
Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second. If a global key (such as Insert or F1) was pressed while ctrl was toggled on, it would be sent to the current activity, not caught by Sugar. This would allow legacy applications which needed these keys to function.&lt;br /&gt;
&lt;br /&gt;
All other keys would have their conventional meaning, except for num lock. The number pad would always be numbers, and pressing num lock would cause the machine to make a loud farting noise.&lt;br /&gt;
&lt;br /&gt;
proposal by [[User:Homunq|Homunq]] 21:06, 22 March 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewer Comments:&#039;&#039;&#039;            &amp;lt;!-- leave this line --&amp;gt;&lt;br /&gt;
::http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03332.html&lt;br /&gt;
::[&amp;lt;span class=&amp;quot;plainlinks&amp;quot;&amp;gt;[{{fullurle:index.php|title=Talk:Design_Team/Vision/Proposals/Keyboard_Action&amp;amp;action=edit&amp;amp;section=1}} edit]&amp;lt;/span&amp;gt;] [[Talk:Design_Team/Vision/Proposals/Keyboard_Action#discoverable,_consistent,_lazy-programmer_keyboard_shortcuts | comments on talk page]]&lt;br /&gt;
&lt;br /&gt;
::    &amp;lt;!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Development_Team/Almanac/sugar.graphics.toolbutton&amp;diff=27896</id>
		<title>Development Team/Almanac/sugar.graphics.toolbutton</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Development_Team/Almanac/sugar.graphics.toolbutton&amp;diff=27896"/>
		<updated>2009-04-23T18:02:26Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* How do I add a keyboard shortcut to my tool button? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Almanac}}&lt;br /&gt;
= Class: ToolButton ([http://www.pygtk.org/docs/pygtk/ gtk.ToolButton]) =&lt;br /&gt;
&lt;br /&gt;
Sugar tool buttons can be added to toolbars and used to control various activity processes. Some common tool button tasks are outlined below. &lt;br /&gt;
&lt;br /&gt;
=== How do I create my own custom tool button? ===&lt;br /&gt;
There are several steps you need to follow in order to create a tool button:&lt;br /&gt;
# Import the ToolButton class from the sugar.graphics.toolbutton package. &lt;br /&gt;
# If you intend to have an icon for your tool button, then create an &amp;quot;icons&amp;quot; directory in your activity directory and put the icon (which is a .svg file) in to that directory. For example, the code below uses an icon called &amp;quot;edit-custom&amp;quot; that accesses an edit-custom.svg file saved in the icons directory for the activity. Here is a link with information on how to create the svg files you will need: [[Making_Sugar_Icons]]&lt;br /&gt;
# Use the code below to guide you on how to then create your button programmatically and add it to a tool bar (we add it to an EditToolbar object that was presumably created already in our code). &lt;br /&gt;
&lt;br /&gt;
        from sugar.graphics.toolbutton import ToolButton&lt;br /&gt;
        ...&lt;br /&gt;
        #### CUSTOM TOOL BUTTON  &lt;br /&gt;
        #Create a custom tool button and add it to the edit toolbar&lt;br /&gt;
        customButton = ToolButton(&#039;edit-custom&#039;)&lt;br /&gt;
        customButton.set_tooltip(_(&#039;Custom&#039;))&lt;br /&gt;
        self._edit_toolbar.insert(customButton, -1)&lt;br /&gt;
        customButton.show()&lt;br /&gt;
&lt;br /&gt;
=== How do I connect my tool button to a callback? ===&lt;br /&gt;
The following code fragment connects a button to a callback ... &lt;br /&gt;
&lt;br /&gt;
        #When the customButton fires a &amp;quot;clicked&amp;quot; event, call self._custom_clicked_cb&lt;br /&gt;
        customButton.connect(&#039;clicked&#039;, self._custom_clicked_cb)&lt;br /&gt;
&lt;br /&gt;
... which is then defined elsewhere in the class. &lt;br /&gt;
    #CALLBACK METHOD&lt;br /&gt;
    def _custom_clicked_cb(self, widget):&lt;br /&gt;
        #Begin any callback code here&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== What is a tooltip and how do I set it for my tool button? ===&lt;br /&gt;
A tooltip is a brief textual description of a tool button that pops up when the mouse cursor is on the toolbutton and the user right-clicks. It is meant to be descriptive so that a user understands what a toolbutton does if it isn&#039;t immediately obvious from the icon. (Note that in the example below, the gettext syntax is used so that the tooltip will be included in the POT file for the project and thus it can be localized.)&lt;br /&gt;
&lt;br /&gt;
      #Set the tooltip for the customButton to &amp;quot;Custom&amp;quot;&lt;br /&gt;
      customButton.set_tooltip(_(&#039;Custom&#039;))&lt;br /&gt;
&lt;br /&gt;
=== How do I reset the icon displayed for my tool button? ===&lt;br /&gt;
Your first argument to the constructor for the ToolButton class will set the initial icon used for your tool button. If you decide to change your tool button&#039;s icon later, then you must get a handle on the tool button object and do the following:&lt;br /&gt;
&lt;br /&gt;
        #Reset the icon displayed for customButton&lt;br /&gt;
        customButton.set_icon(&amp;quot;edit-custom&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
=== How do I add a keyboard shortcut to my tool button? ===&lt;br /&gt;
In the example below, we add the Ctrl-b short cut to our custom button. (Activity authors are encouraged to use &amp;lt;ctrl&amp;gt; for most shortcuts.)&lt;br /&gt;
&lt;br /&gt;
        #Add keyboard shortcut for customButton&lt;br /&gt;
        customButton.props.accelerator = &#039;&amp;lt;ctrl&amp;gt;b&#039;&lt;br /&gt;
&lt;br /&gt;
If you want to enable translators to override the shortcut, use the gettext syntax so that an entry in the POT file is generated (See [[Development_Team/Almanac/Internationalization]] for details):&lt;br /&gt;
&lt;br /&gt;
        customButton.props.accelerator = _(&#039;&amp;lt;ctrl&amp;gt;b&#039;)&lt;br /&gt;
&lt;br /&gt;
If you want to use symbols in you shortcuts, you&#039;ll need to refer to the X11 keysymdefs (/usr/include/X11/keysymdef.h), e.g., to use a &amp;quot;+&amp;quot; as a shortcut, you&#039;d refer to &amp;lt;code&amp;gt;#define XK_plus 0x002b /* U+002B PLUS SIGN */&amp;lt;/code&amp;gt; and use the string after the &amp;lt;code&amp;gt;XK_&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
        customButton.props.accelerator = _(&#039;&amp;lt;ctrl&amp;gt;plus&#039;)&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27368</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27368"/>
		<updated>2009-04-13T21:47:13Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;do&#039;&#039; 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&#039;d like to talk to you about participating in Sugar outside of GSoC.&lt;br /&gt;
&lt;br /&gt;
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&#039;ve received are things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Sunday Apr 1 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=1&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]: [[User:example|example]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example - I used &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; to add a signature, and added any special requests after.)&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira, [[User:Aa|aa]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]: Vamsi Krishna Davuluri (iwikiwi)&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC: &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC: Lucian Branescu (lucian1900)&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:Aa|aa]], [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Sayamindu Dasgupta, Assim Deodia ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27364</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27364"/>
		<updated>2009-04-13T18:44:07Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Sunday Apr 1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;do&#039;&#039; 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&#039;d like to talk to you about participating in Sugar outside of GSoC.&lt;br /&gt;
&lt;br /&gt;
Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Sunday Apr 1 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=1&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]: [[User:example|example]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example - I used &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; to add a signature, and added any special requests after.)&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC: Lucian Branescu (lucian1900)&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Sayamindu Dasgupta ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27363</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27363"/>
		<updated>2009-04-13T18:43:47Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Sunday Apr 1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;do&#039;&#039; 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&#039;d like to talk to you about participating in Sugar outside of GSoC.&lt;br /&gt;
&lt;br /&gt;
Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Sunday Apr 1 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=1&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]: [[User:example|example]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example - I used &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; to add a signature, and added any special requests after.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC: Lucian Branescu (lucian1900)&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Sayamindu Dasgupta ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27360</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27360"/>
		<updated>2009-04-13T18:11:53Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;do&#039;&#039; 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&#039;d like to talk to you about participating in Sugar outside of GSoC.&lt;br /&gt;
&lt;br /&gt;
Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Sunday Apr 1 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=1&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]: [[User:Homunq|Homunq]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC: Lucian Branescu (lucian1900)&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Sayamindu Dasgupta ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27359</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27359"/>
		<updated>2009-04-13T17:40:18Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;do&#039;&#039; 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&#039;d like to talk to you about participating in Sugar outside of GSoC.&lt;br /&gt;
&lt;br /&gt;
Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC: Lucian Branescu (lucian1900)&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Sayamindu Dasgupta ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27356</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27356"/>
		<updated>2009-04-13T14:59:04Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Thurs Apr 16 (Wed 15 in the western hemisphere) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, please contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27352</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27352"/>
		<updated>2009-04-13T14:25:32Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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.)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, please contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:  &lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, [[User:BryanWB|BryanWB]] ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]: Andrés&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC: &lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27289</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27289"/>
		<updated>2009-04-12T23:57:21Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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.)&lt;br /&gt;
&lt;br /&gt;
Interviews will be conducted over IRC; even hours on #sugar-interview0 and half-hours on #sugar-interview1 .&lt;br /&gt;
&lt;br /&gt;
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, please contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, Andrés Ambrois, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]: Andrés&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27287</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27287"/>
		<updated>2009-04-12T23:41:21Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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 accomadate your chosen time or reschedule at a convenient time for you.)&lt;br /&gt;
&lt;br /&gt;
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, please contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=0&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 0000 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=16&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=18&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1800 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27286</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27286"/>
		<updated>2009-04-12T23:39:59Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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 accomadate your chosen time or reschedule at a convenient time for you.)&lt;br /&gt;
&lt;br /&gt;
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we&#039;d really love to have you working on, even if we don&#039;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&#039;t give you a slot, please contact us on the sugar-devel or gsoc mailing list and we&#039;ll work something out.&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* 0000 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* 1800 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27285</id>
		<title>Summer of Code/Interviews</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&amp;diff=27285"/>
		<updated>2009-04-12T23:33:30Z</updated>

		<summary type="html">&lt;p&gt;Homunq: New page: We would like to interview the top 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 me...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We would like to interview the top 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 accomadate your chosen time or reschedule at a convenient time for you.)&lt;br /&gt;
&lt;br /&gt;
== Wed Apr 15 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* [http://www.timeanddate.com/counters/customcounter.html?day=15&amp;amp;month=04&amp;amp;year=2009&amp;amp;hour=14&amp;amp;min=0&amp;amp;sec=0&amp;amp;p0=0 1400 UTC]:&lt;br /&gt;
&lt;br /&gt;
* 1430 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1500 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1530 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* 0000 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0030 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0100 UTC:&lt;br /&gt;
&lt;br /&gt;
* 0130 UTC:&lt;br /&gt;
&lt;br /&gt;
== Thurs Apr 16 ==&lt;br /&gt;
&lt;br /&gt;
Mentors attending: Jameson Quinn, ...&lt;br /&gt;
&lt;br /&gt;
* 1800 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1830 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1900 UTC:&lt;br /&gt;
&lt;br /&gt;
* 1930 UTC:&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=26564</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=26564"/>
		<updated>2009-04-08T13:46:15Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* more */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link to this subsection, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== Competing proposals ==&lt;br /&gt;
&lt;br /&gt;
Your proposal is one of two or more proposals to attack the same problem. In order to decide, we will be looking at the following, in more or less this order:&lt;br /&gt;
&lt;br /&gt;
* Clarity, specificity, and attainability of the deliverables mentioned in your timeline.&lt;br /&gt;
&lt;br /&gt;
* Any useful patches you submit to Sugar or one of our upstream projects. Please link such patches in comments on your application.&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
* Your community involvement during this period. This includes responsiveness to any comments on your application or on your proposal&#039;s talk page; your own helpful comments on other application&#039;s talk pages; and any other community tasks such as bug triage or wiki cleanup. Feel free to call attention to any of this in your application, but don&#039;t let it get in the way of the above two points.&lt;br /&gt;
&lt;br /&gt;
* Your own qualifications, as far as we can evaluate from your application.&lt;br /&gt;
&lt;br /&gt;
Note also that we will consider accepting two good applications in the same general problem space if we consider them to be distinct enough. &lt;br /&gt;
&lt;br /&gt;
Please act accordingly.&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=26563</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=26563"/>
		<updated>2009-04-08T13:43:38Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* more */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link to this subsection, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== more ==&lt;br /&gt;
&lt;br /&gt;
Your proposal is one of two or more proposals to attack the same problem. In order to decide, we will be looking at the following, in more or less this order:&lt;br /&gt;
&lt;br /&gt;
* Clarity, specificity, and attainability of the deliverables mentioned in your timeline.&lt;br /&gt;
&lt;br /&gt;
* Any useful patches you submit to Sugar or one of our upstream projects. Please link such patches in comments on your application.&lt;br /&gt;
&lt;br /&gt;
* Your community involvement during this period. This includes responsiveness to any comments on your application or on your proposal&#039;s talk page; your own helpful comments on other application&#039;s talk pages; and any other community tasks such as bug triage or wiki cleanup. Feel free to call attention to any of this in your application, but don&#039;t let it get in the way of the above two points.&lt;br /&gt;
&lt;br /&gt;
* Your own qualifications, as far as we can evaluate from your application.&lt;br /&gt;
&lt;br /&gt;
Please act accordingly.&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2009/Marbles&amp;diff=26118</id>
		<title>Summer of Code/2009/Marbles</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2009/Marbles&amp;diff=26118"/>
		<updated>2009-04-08T00:44:17Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;THIS IS A DUPLICATE APPLICATION, JUST USE [[Marbles]] PLEASE.&lt;br /&gt;
&lt;br /&gt;
=== About Me ===&lt;br /&gt;
&lt;br /&gt;
Q1.&#039;&#039;&#039; What is your name? &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. Puneet Girdhar&lt;br /&gt;
&lt;br /&gt;
Q2. &#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. puneetgirdhar.iiit@gmail.com&lt;br /&gt;
&lt;br /&gt;
Q3. &#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. puneet&lt;br /&gt;
&lt;br /&gt;
Q4. &#039;&#039;&#039;What is your IRC nickname?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. chasedspeed&lt;br /&gt;
&lt;br /&gt;
Q5. &#039;&#039;&#039;What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you&#039;d prefer.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. hindi. good at english though.&lt;br /&gt;
&lt;br /&gt;
Q6. &#039;&#039;&#039;Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans.Hyderabad, India-500032. In summer, I can devote full time on open source activity. Any time suits me fine.&lt;br /&gt;
&lt;br /&gt;
Q7. &#039;&#039;&#039;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&lt;br /&gt;
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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans.This would be my first active participation in open source development. I have worked on variety of projects ranging from web services, mobile development in j2me, python web server managment. I guess, I knew about GSOC before but was busy in learning open source technologies so could not apply before, but now after gaining enough experience about project development and technical skills I didn&#039;t want to lose the opportunity to contribute back to open source community.I want to get started here and wish to continue even after GSOC.&lt;br /&gt;
&lt;br /&gt;
=== About My project ===&lt;br /&gt;
&lt;br /&gt;
Q8. &#039;&#039;&#039; What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. Marbles : Shape the imagination&lt;br /&gt;
&lt;br /&gt;
Q9. &#039;&#039;&#039; 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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans.We are supporting children imagination and trying to realize them in digtal world. Students often love to indulge themselves in various acivities ranging from playing to building stuff, to management . These are nothing but their imaginative reach trying to make it real. These creativity are the most important one and the most beneficial in child development. Computers on other hand are meant for catching imagination and creating artificial reality, then why shouldn&#039;t we attach them both. We would be using computers digital approach to support child creativity. Children can play games, learn programming , build application, learn graphics and many other activities.&lt;br /&gt;
&lt;br /&gt;
Use case scenarios :&lt;br /&gt;
&lt;br /&gt;
Students can use this project for&lt;br /&gt;
# create a simple UI application with simple drag and drop widgets.&lt;br /&gt;
# they would be able to resize the widget, reorder them and associate some event handlers to the widgets.&lt;br /&gt;
# Programming support would be given for advanced students where they can test and improve their programming skills for beginners, a step-by-step instruction sets for introducing them in programming.&lt;br /&gt;
# We can go for sound support with gstreamer library, where we can interact the program with simple sounds, since children get attracted to sound &amp;lt;br&amp;gt;more easily than text&lt;br /&gt;
# Help Manual to get started for students. Special care will be taken for information supplied, they would be concise and expressive.&lt;br /&gt;
&lt;br /&gt;
This project also targets the developers, they can use our application to&lt;br /&gt;
# add / remove activity&lt;br /&gt;
# modify activity, Activity modules would be independent of architecture and easily modifiable to suit current needs.&lt;br /&gt;
# sugar bot support for unit-testing&lt;br /&gt;
# debugger integration with gui to facilitate debugging the activity.&lt;br /&gt;
&lt;br /&gt;
We can associate various group activities among students to encourage them in developing environment.&lt;br /&gt;
Technologies I will be using are pygtk, XML parsers ( if sharing of information is required ) . Pygtk, gives a gtk libraries support which we can code them to interact with the enviornment and develop UI applications. XML communication would be required if there is need to transfer the information from one end to another. Some of key points would be :&lt;br /&gt;
&lt;br /&gt;
# Primary aim would be to provide basic learning experience in UI application with minimal programming efforts.&lt;br /&gt;
# Secondary aim would be to increase Scope for development for future developers.&lt;br /&gt;
# Application would be built as simple as possible with highlighting and attractive features.&lt;br /&gt;
# Sharing of code over network, integrating of code in program directly.&lt;br /&gt;
# Exception handlers, should be interactive for users and should take minor decisions automatically.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
        &lt;br /&gt;
==== Technical Approach ==== &lt;br /&gt;
&lt;br /&gt;
Below is the technical abstract for Marbles:&lt;br /&gt;
:[[Image:marbles-flowchart.png|left| Marlbes-development environment.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Here visual UI representations gives an option to select widgets, authoring tool will assist the users to place the widgets on frame and also do some prechecks on UI widget compatibility.Program generator then generates the optimized code based on UI types, positions and associates event handlers to the widgets. Views should be handled independently and it includes final checks on widgets too. History generation is being done side by side to facilitate recoveries if error occurs and finally, output generation ( both UI and code output ) . Code output from the software will be stored in specific directories or in database.&lt;br /&gt;
&lt;br /&gt;
Database comes into picture while history creation with simple as undo/redo or more complex project development stages. Typically database would store the fields like&lt;br /&gt;
&lt;br /&gt;
#Table: Widget&lt;br /&gt;
#*Fields: Widget id,name,label,icon, height, width, position,parent_container id ,visible,focus-type, param1,param2&lt;br /&gt;
#*Widget table will contain widget id , it&#039;s name,label,positional parameters, id to its paraent container, and other parameters specific&amp;lt;br&amp;gt;to widget functionality like for checkbox we could have parameters like &amp;quot;default check&amp;quot;. This table includes all type of widgets i.e.&amp;lt;br&amp;gt;containers, menu, buttons, checkbox etc&lt;br /&gt;
#Events&lt;br /&gt;
#*Fields: Eventid, type,signalid, signal-handler,object,widget-id(foreign key),params&lt;br /&gt;
#*Events table will register the events associated with the widgets. Note that signal handler would be called as object.signal-handler() with&amp;lt;br&amp;gt; parameters if necessary.  &lt;br /&gt;
#Navigation-Views&lt;br /&gt;
#*Fields: Widget-id,pos-x,pos-y,col-span,row-span,padding,Expanding(boolean), shrink(boolean), colorfill(boolean), params&lt;br /&gt;
#*This gives option to handle view effectively. Options are id, postions, span space, padding space, expanding ( yes/ no ), shrinking&amp;lt;br&amp;gt;(yes/no), color fill and other parameters. This table would be mainly responsible for generating views in desktop UI.&lt;br /&gt;
#Navigation-main &lt;br /&gt;
#*Fields: Widgetid,name,description,activate(boolean),children-id(foreign key),delete(boolean),params&lt;br /&gt;
#*This table will be the database of UI application and UI graphics can be straight generated using this table. This table would be overwritten with widgetids everytime, when an object is added to on VISUAL UI. this contains field like widget id,&amp;lt;br&amp;gt;name desc, chidren-id ( widget that comes under it ) and other functional or positional parameters. delete column will help in faking delete&amp;lt;br&amp;gt;option( more on this later ).&lt;br /&gt;
#*This table can also be shared in network and associated with other UI applications. Here XML messaging can be used with DOM/SAX parser support in this application.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Description&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Initially, navigation-main row will be initiated with widget-id say 0 and delete will be false &lt;br /&gt;
When user drags an widget on canvas, new widget will be created and a new entry comes in navigation-main table. Similarly children-widgets are created and subsequent entries will be given in specific tables. In this way, a whole tree-view of UI application would then be saved in database.&lt;br /&gt;
For undo operation, navigation-row entry for &amp;quot;delete&amp;quot; can be set to true, similarly for redo operation, entry would be false again.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How output is generated&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
program generator will read navigation-main and widgets specified by user will be initiated with given options. Navigation-view will then be fetched and widgets will then be arranged according to view-instructions. &lt;br /&gt;
Code generated will be temporarily stored in files ( say /tmp) , can be permanent stored if user wants to save the UI-application.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Special care will be given on debugging facility. since pygtk is used in UI application, sugar-bot integration would not be difficult to achieve. I will also try to include modules for sugar-bot debugging facility to facilitated direct unit-testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q10.  &#039;&#039;&#039; 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&#039;s good to have a plan at the beginning so you have an idea of where you&#039;re headed.) Note that you should probably plan to have something &amp;quot;working and 90% done&amp;quot; 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.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ans.&lt;br /&gt;
In summer, I plan to follow the following schedule:&lt;br /&gt;
&lt;br /&gt;
#Preparation phase( Time : April 25 - may25 )&lt;br /&gt;
#*gathering requirements of the project&lt;br /&gt;
#*getting involved with Mentor in verifying and validating the requirements.&lt;br /&gt;
#*Architectural design / Pseudo code.&lt;br /&gt;
#*This phase, I would be communicating with people as much as possible, getting requirements and verifying &amp;lt;br&amp;gt; with people or community. I would also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project &amp;lt;br&amp;gt; development.I am sure to get community support on this very interesting project.&lt;br /&gt;
#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )&lt;br /&gt;
#*divisions for coding timeline&lt;br /&gt;
#* decide approach for programming&lt;br /&gt;
#* actual coding, testing accordingly&lt;br /&gt;
#* documenting code parallely    &lt;br /&gt;
#* periodically sharing information with mentors and community members&lt;br /&gt;
#* This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can devote&amp;lt;br&amp;gt; more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.&lt;br /&gt;
#Testing Phase ( Time: July7- July 25 )&lt;br /&gt;
#* full testing of system with different phases&lt;br /&gt;
#* use coverage analysis to know the redundance code and improving it further&lt;br /&gt;
#* fixing bugs if any&lt;br /&gt;
#* Last minute changes before final submission&lt;br /&gt;
#* finish any documentation steps if left.&lt;br /&gt;
#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and I really like this &amp;lt;br&amp;gt; efficency measurement whicha also helps a lot in improving run-time. I will go for different testing tools on program, Some tools I would like&amp;lt;br&amp;gt; to go with&lt;br /&gt;
#*coverage or flegleaf tools for anlaysis.&amp;lt;br&amp;gt;&lt;br /&gt;
#*I will use boost algorithms to improve run-time if it comes under requirement. &lt;br /&gt;
#Finalizing phase / Revision ( Time: from August 1 to END.)&lt;br /&gt;
#* review of code/ algorithm&lt;br /&gt;
#* production of coverage reports, analysis, performance etc.&lt;br /&gt;
#* discussions on limitations of software and beneficials.&lt;br /&gt;
#* preparing final deployments for various systems.&amp;lt;br&amp;gt;&lt;br /&gt;
#* Documentation stuffs would go in this phase&lt;br /&gt;
&lt;br /&gt;
Time line: Seems very little time to do so many things, but I will try to give the best from my side.&lt;br /&gt;
&lt;br /&gt;
I have worked on variety of projects ranging from web application, mobile j2me midlets, Web server management( python project ) and desktop application. One of the interesting projects I worked on is &amp;quot;cross platform windows explorer&amp;quot; which I built in python using wxwidget, in which we handled the issues like portability, searching and UI designs. If I am not exagerating, that would not be wrong to say that I am a fast learner.&lt;br /&gt;
&lt;br /&gt;
Believe me, I have that talent needed to build and design a complex system for customers. Below are some of the projects I worked on&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Shallow file browser&#039;&#039;&#039;: cross platform browser&lt;br /&gt;
* &#039;&#039;&#039;Multithreaded multi media-server&#039;&#039;&#039; : A multithreaded cross platform media-server for streaming podcast or mulitimedia contents to mediadevices.&amp;lt;br&amp;gt; It is currently being used by medicare services to stream health podcasts to the users.&lt;br /&gt;
* &#039;&#039;&#039;Mobile Softwares&#039;&#039;&#039;: I had done some freelance work in mobile computation last semester. Major projects, I was associated with are Mobile &amp;lt;br&amp;gt; Shopping, SRV navigation tool for medicare services (SRV is an open source hardware(robot) for education purposes).&lt;br /&gt;
* &#039;&#039;&#039;Web Development &amp;amp; Services&#039;&#039;&#039;: I have been actively involved in web-development from past 1 year and used Ruby on rails and Django for development. Django, by&amp;lt;br&amp;gt; far, was among my best tool for Web-UI applications.&lt;br /&gt;
* Minor projects on kernel implementation ( as a part of OS course ), Database managment projects and others.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; My &amp;quot;Open Source&amp;quot; activites &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* Check out the source code of shallow file browser at http://code.google.com/p/shallow-file-browser. Do check the snapshot of browser in action.&lt;br /&gt;
* Minute-Shell: Well, it&#039;s a part of my course project. I created a small program to emulate linux shell. This code is hosted at http://code.google.com/p/minute-shell/ .&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Me and the community ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q11. &#039;&#039;&#039; 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.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. This project support children creativity and imagination. These small games, development activity will surely help them to become problem solvers, innovators, and creative thinkers. These activities will also help the children to develop many important skills that boost a child&#039;s learning and success.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q12. &#039;&#039;&#039; 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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. That would be a great idea to go with. I&#039;ve been working in NGO for primary children education called &amp;quot;ASHA-KIRAN&amp;quot; in our college and it would a great learning experience for them. Here, in hyderabad, We have a language problem, they don&#039;t understand hindi, my mother tongue, and I don&#039;t understand, telgu ( local language ). So, I always use different activities to teach them like sound creation, drawing, Word dictionary, some local plays etc. I believe in case of language problems like India, We should teach the children as:&lt;br /&gt;
 &lt;br /&gt;
# Alphabet creation, as a drawing practice&lt;br /&gt;
# Sound, give alphabets some sound, try to echo them loudly, may be in funnier way.&lt;br /&gt;
# Try to associate meaning to words, here imagination comes into play. I use some stories behind words, or pictures  &lt;br /&gt;
# Last, use them in sentence.&lt;br /&gt;
&lt;br /&gt;
I can associate these features in my project and sugar lab can help us to provide technical equipments to teach children. We already have a good infrastructure in campus, so I will start using my project even in development stage with them and report the status to sugar community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q13. &#039;&#039;&#039; What will you do if you get stuck on your project and your mentor isn&#039;t around?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. I have been using open source projects for quite a long time and I know, we always get stuck with some problem may be installation, compiling, syntax error, many more but I guess this is where the interesting part begins and open source community comes into play. In my views, we always learn new things about the error/software if we ask doubts in community. So, if I ever get stuck on the project, I will raise my doubts in mailing lists, request clearifications in irc chat, write in blog or on some related community sites where I can get any assistant from.&lt;br /&gt;
&lt;br /&gt;
Other assistant I am sure to get it from my seniors, they all have been participating in GSOC from past years and would love to assist me if need occurs.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Q14. &#039;&#039;&#039; 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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. I love interactive with people and I will keep community members duly informed. I can try following things to work this out&lt;br /&gt;
&lt;br /&gt;
* Chatting on IRC chat&lt;br /&gt;
* Mailing lists&lt;br /&gt;
* tracking specific person or related to the area personally via email.&lt;br /&gt;
* Posting queries on blog&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
[[Image:puneetgirdhar.png|thumb|right| Here is my Development environment.]]&lt;br /&gt;
&lt;br /&gt;
Q15. &#039;&#039;&#039; 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 &amp;quot;Restart.&amp;quot; See the image on the right for an example. It&#039;s normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans.  I am a fedora loving guy and installed sugar system on my fedora. I googled for the installation and successfully completed the following tasks&lt;br /&gt;
* Installed the system using yum packages.&amp;lt;br&amp;gt;&lt;br /&gt;
This is just double click installation like windows. But I could not find the development procedure for rpm packages.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Built using source.&amp;lt;br&amp;gt;&lt;br /&gt;
I used jhbuild to install and update the source code needed for the sugar development. I tested it by creating some activities given on wiki&amp;lt;br&amp;gt; page of sugar lab and it was working fine.&amp;lt;br&amp;gt;&lt;br /&gt;
I&#039;ve started exploring things and really looking forward for a good open source development.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q16. &#039;&#039;&#039; Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. As a child, I had a great interest in science and was more curious to know everything. One thing I would like to share is, When I was in 8th standard, I was more impressed by Einsten-theory &amp;quot;One theory for every theories&amp;quot; and still I am. I remember discussing my new science theories on unification of world and discoveries with my science teacher and which ofcourse he won&#039;t like and always got irritated, but what he always suggested me, is to read &amp;amp; analyze before coming to conclusions. This habit of me is still continuing. Now the views have changed, questions are different but thirst for knowing things is still the same. My teacher not only answers my query but it gives me a life time dose to approach for my problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q17. &#039;&#039;&#039; What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ans. medium&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q18.&#039;&#039;&#039; 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?&#039;&#039;&#039;&lt;br /&gt;
   &lt;br /&gt;
Ans. Just for introduction, I am pursuing my BTECH degree from IIIT Hyderabad. I had started using linux from past 2 years and since then I love every bit of it. I also have research interest and working on my research paper on &amp;quot;simulation of rigid blocks during earthquake&amp;quot;. I am an &lt;br /&gt;
active coder in SPOJ and topcoder and have a strong python programming skills. I have also worked as an intern in california based company.&lt;br /&gt;
&amp;quot;buddibot&amp;quot; developing medicare services for elderly people.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;   No matter if I get selected or not, but I love to continue with sugar community.I already registered myself in sugar bug reporting tool and trying to study source code. Please let me know how can I assist to open source community.&amp;lt;br&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Thank You &amp;amp; Regards,&amp;lt;br&amp;gt;&lt;br /&gt;
Puneet.&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25608</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25608"/>
		<updated>2009-04-05T21:28:56Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Don&amp;#039;t reinvent the wheel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link to this subsection, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== more ==&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25607</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25607"/>
		<updated>2009-04-05T21:27:47Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* yet more */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link here, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== more ==&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25606</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25606"/>
		<updated>2009-04-05T21:27:18Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link here, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== more ==&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC proposals]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25603</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25603"/>
		<updated>2009-04-05T21:20:13Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Don&amp;#039;t reinvent the wheel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link here, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;br /&gt;
&lt;br /&gt;
== more ==&lt;br /&gt;
&lt;br /&gt;
== and more ==&lt;br /&gt;
&lt;br /&gt;
== yet more ==&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25602</id>
		<title>Summer of Code/Application review notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Application_review_notes&amp;diff=25602"/>
		<updated>2009-04-05T21:19:40Z</updated>

		<summary type="html">&lt;p&gt;Homunq: New page: Thank you to everyone who applied for GSoC this year. Here are some comments:  *Please try to watch your application&amp;#039;s talk page, as well as the comments in google&amp;#039;s web app, and respond a...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thank you to everyone who applied for GSoC this year. Here are some comments:&lt;br /&gt;
&lt;br /&gt;
*Please try to watch your application&#039;s talk page, as well as the comments in google&#039;s web app, and respond as quickly as possible. If language is a barrier, it is better to respond in Spanish than not at all, although English is preferred.&lt;br /&gt;
&lt;br /&gt;
== Don&#039;t reinvent the wheel ==&lt;br /&gt;
When working in open source, the idea is to get as much done with as little work as possible. That means you need the ability to find, evaluate, and adapt existing code to your purposes. Some (not all) of your applications do not give adequate attention to this issue. If we send you a link here, please respond by:&lt;br /&gt;
&lt;br /&gt;
*Searching (in places like sourceforge and google code) for existing tools which do something similar to what you propose&lt;br /&gt;
&lt;br /&gt;
*Evaluating their usefulness, including the health of the code, the approximate size of dependencies they would add to Sugar, and their adaptability for your purpose.&lt;br /&gt;
&lt;br /&gt;
*Figuring out, as specifically as possible in the time you have, how they&#039;d fit into sugar, and where you&#039;d have to change the tool or sugar itself to make that happen.&lt;br /&gt;
&lt;br /&gt;
Tell us something about what you find in each step. Even &amp;quot;I found project xxx but it&#039;s defunct, and yyy but it doesn&#039;t fit at all because zzz&amp;quot; is useful to us to see that you can do this work.&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=EduKT_improvement_proposal&amp;diff=25417</id>
		<title>EduKT improvement proposal</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=EduKT_improvement_proposal&amp;diff=25417"/>
		<updated>2009-04-04T08:31:56Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;About you&lt;br /&gt;
&lt;br /&gt;
   1. Arturo Bolaños Victoria&lt;br /&gt;
   2. dark.arturo@gmail.com&lt;br /&gt;
   3. arturoblack&lt;br /&gt;
   4. arturoblack&lt;br /&gt;
   5. spanish&lt;br /&gt;
   6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.) &lt;br /&gt;
&lt;br /&gt;
                    &lt;br /&gt;
&lt;br /&gt;
   1. 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?&lt;br /&gt;
          to improve my level of programming and contribute to the FLOSS&lt;br /&gt;
&lt;br /&gt;
About your project&lt;br /&gt;
&lt;br /&gt;
   1. What is the name of your project? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   1.&lt;br /&gt;
      Edukt can mejorarce with the aforementioned option to drag and drop functionality and audio, but also can be add a function that controls the order in which images are drawn on the control so that you can put one over another Also be possible to add ocion of the resized images that pull to have better control on the program The basic idea is to take is to rebuild the ability to drag and drop addition of new features that give the program&lt;br /&gt;
      of the features already mentioned.&lt;br /&gt;
   2. 1 Week&lt;br /&gt;
           study on the book to use for the project.&lt;br /&gt;
      2 to 3 weeks&lt;br /&gt;
           Presentation of the first step.&lt;br /&gt;
      4 °&lt;br /&gt;
           progress and implementation of&lt;br /&gt;
      8 weeks&lt;br /&gt;
           evidence o&lt;br /&gt;
      12 weeks&lt;br /&gt;
         &lt;br /&gt;
   3.&lt;br /&gt;
      I have experience developing applications with GTK python using pygtk and glade&lt;br /&gt;
         Managing images and text on graphical control, and management know the libreias of Pango and cairo.&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC proposals]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=EduKT_improvement_proposal&amp;diff=25415</id>
		<title>EduKT improvement proposal</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=EduKT_improvement_proposal&amp;diff=25415"/>
		<updated>2009-04-04T08:31:18Z</updated>

		<summary type="html">&lt;p&gt;Homunq: User:Arturoblack moved to EduKT improvement proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;About you&lt;br /&gt;
&lt;br /&gt;
   1. Arturo Bolaños Victoria&lt;br /&gt;
   2. dark.arturo@gmail.com&lt;br /&gt;
   3. arturoblack&lt;br /&gt;
   4. arturoblack&lt;br /&gt;
   5. spanish&lt;br /&gt;
   6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.) &lt;br /&gt;
&lt;br /&gt;
                    &lt;br /&gt;
&lt;br /&gt;
   1. 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?&lt;br /&gt;
          to improve my level of programming and contribute to the FLOSS&lt;br /&gt;
&lt;br /&gt;
About your project&lt;br /&gt;
&lt;br /&gt;
   1. What is the name of your project? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   1.&lt;br /&gt;
      Edukt can mejorarce with the aforementioned option to drag and drop functionality and audio, but also can be add a function that controls the order in which images are drawn on the control so that you can put one over another Also be possible to add ocion of the resized images that pull to have better control on the program The basic idea is to take is to rebuild the ability to drag and drop addition of new features that give the program&lt;br /&gt;
      of the features already mentioned.&lt;br /&gt;
   2. 1 Week&lt;br /&gt;
           study on the book to use for the project.&lt;br /&gt;
      2 to 3 weeks&lt;br /&gt;
           Presentation of the first step.&lt;br /&gt;
      4 °&lt;br /&gt;
           progress and implementation of&lt;br /&gt;
      8 weeks&lt;br /&gt;
           evidence o&lt;br /&gt;
      12 weeks&lt;br /&gt;
         &lt;br /&gt;
   3.&lt;br /&gt;
      I have experience developing applications with GTK python using pygtk and glade&lt;br /&gt;
         Managing images and text on graphical control, and management know the libreias of Pango and cairo.&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Keyboard_shortcuts_proposal&amp;diff=25414</id>
		<title>Keyboard shortcuts proposal</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Keyboard_shortcuts_proposal&amp;diff=25414"/>
		<updated>2009-04-04T08:09:22Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Abstract:&lt;br /&gt;
Help to the user with the shortcuts representing those in the window, allowing fast actions and a better work.....&lt;br /&gt;
&lt;br /&gt;
Content:&lt;br /&gt;
&lt;br /&gt;
All you should put here is a link to your application on our wiki, such as http://wiki.sugarlabs.org/go/Summer_of_Code/Student_application_template . If you consider any of the following information private, you can include it here instead; otherwise, just erase the following.&lt;br /&gt;
&lt;br /&gt;
About you&lt;br /&gt;
&lt;br /&gt;
1. What is your name?&lt;br /&gt;
&lt;br /&gt;
Luciano Jesus Palomino Jauregui&lt;br /&gt;
&lt;br /&gt;
2. What is your email address?&lt;br /&gt;
&lt;br /&gt;
jesusjpj@gmail.com&lt;br /&gt;
&lt;br /&gt;
3. What is your Sugar Labs wiki username?&lt;br /&gt;
&lt;br /&gt;
jesusjpj&lt;br /&gt;
&lt;br /&gt;
4. What is your IRC nickname?&lt;br /&gt;
&lt;br /&gt;
LucianoP&lt;br /&gt;
&lt;br /&gt;
5. What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you&#039;d prefer.)&lt;br /&gt;
&lt;br /&gt;
Spanish&lt;br /&gt;
&lt;br /&gt;
6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)&lt;br /&gt;
&lt;br /&gt;
UTC / GMT - 5 h&lt;br /&gt;
&lt;br /&gt;
7. 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?&lt;br /&gt;
&lt;br /&gt;
Localizate OpenOffice.org.&lt;br /&gt;
*Reference: neosergio@openoffice.org (Coordinador General OpenOffice.org Perú) &lt;br /&gt;
&lt;br /&gt;
War Game Simulator Tarapaca-Peruvian Army.(Python, GTK y SQLite)&lt;br /&gt;
*Reference: alfonsodg@gmail.com (Asesor Tecnologico del Ejercito del Perú) &lt;br /&gt;
&lt;br /&gt;
I contributed code to the base Ice3(Python)&lt;br /&gt;
* Reference: https://launchpad.net/~ice3-developers (Luciano Jesus/jesusjpj) &lt;br /&gt;
&lt;br /&gt;
About your project&lt;br /&gt;
&lt;br /&gt;
1. What is the name of your project?&lt;br /&gt;
&lt;br /&gt;
Shortcut Helpers&lt;br /&gt;
&lt;br /&gt;
2. 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?&lt;br /&gt;
&lt;br /&gt;
3. 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&#039;s good to have a plan at the beginning so you have an idea of where you&#039;re headed.) Note that you should probably plan to have something &amp;quot;working and 90% done&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4. 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.&lt;br /&gt;
 	&lt;br /&gt;
My experience developing Simulator Game Wars Tarapaca (which use Python and GTK), how close I am to implement the project with OLPC Sugar (The kids in my province are benefiting from OLPC) and ease of purchase that I have knowledge makes it a potential candidate to complete this project.&lt;br /&gt;
 &lt;br /&gt;
5. What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)&lt;br /&gt;
&lt;br /&gt;
medium&lt;br /&gt;
&lt;br /&gt;
6. Describe a great learning experience you had as a child.&lt;br /&gt;
&lt;br /&gt;
7. 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?&lt;br /&gt;
&lt;br /&gt;
The children in my country and especially my department are among the beneficiaries of this project so I would put my bit and bring more functionality to Sugar for children to be more efficient with the use of this tool. That will be an additional stimulus for me.&lt;br /&gt;
&lt;br /&gt;
[[Category:2009 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=User:Jesusjpj&amp;diff=25413</id>
		<title>User:Jesusjpj</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=User:Jesusjpj&amp;diff=25413"/>
		<updated>2009-04-04T08:08:21Z</updated>

		<summary type="html">&lt;p&gt;Homunq: User:Jesusjpj moved to Keyboard shortcuts proposal: consistent with other GSoC proposals&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Keyboard shortcuts proposal]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Keyboard_shortcuts_proposal&amp;diff=25412</id>
		<title>Keyboard shortcuts proposal</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Keyboard_shortcuts_proposal&amp;diff=25412"/>
		<updated>2009-04-04T08:08:20Z</updated>

		<summary type="html">&lt;p&gt;Homunq: User:Jesusjpj moved to Keyboard shortcuts proposal: consistent with other GSoC proposals&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Abstract:&lt;br /&gt;
Help to the user with the shortcuts representing those in the window, allowing fast actions and a better work.....&lt;br /&gt;
&lt;br /&gt;
Content:&lt;br /&gt;
&lt;br /&gt;
All you should put here is a link to your application on our wiki, such as http://wiki.sugarlabs.org/go/Summer_of_Code/Student_application_template . If you consider any of the following information private, you can include it here instead; otherwise, just erase the following.&lt;br /&gt;
&lt;br /&gt;
About you&lt;br /&gt;
&lt;br /&gt;
1. What is your name?&lt;br /&gt;
&lt;br /&gt;
Luciano Jesus Palomino Jauregui&lt;br /&gt;
&lt;br /&gt;
2. What is your email address?&lt;br /&gt;
&lt;br /&gt;
jesusjpj@gmail.com&lt;br /&gt;
&lt;br /&gt;
3. What is your Sugar Labs wiki username?&lt;br /&gt;
&lt;br /&gt;
jesusjpj&lt;br /&gt;
&lt;br /&gt;
4. What is your IRC nickname?&lt;br /&gt;
&lt;br /&gt;
LucianoP&lt;br /&gt;
&lt;br /&gt;
5. What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you&#039;d prefer.)&lt;br /&gt;
&lt;br /&gt;
Spanish&lt;br /&gt;
&lt;br /&gt;
6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)&lt;br /&gt;
&lt;br /&gt;
UTC / GMT - 5 h&lt;br /&gt;
&lt;br /&gt;
7. 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?&lt;br /&gt;
&lt;br /&gt;
Localizate OpenOffice.org.&lt;br /&gt;
*Reference: neosergio@openoffice.org (Coordinador General OpenOffice.org Perú) &lt;br /&gt;
&lt;br /&gt;
War Game Simulator Tarapaca-Peruvian Army.(Python, GTK y SQLite)&lt;br /&gt;
*Reference: alfonsodg@gmail.com (Asesor Tecnologico del Ejercito del Perú) &lt;br /&gt;
&lt;br /&gt;
I contributed code to the base Ice3(Python)&lt;br /&gt;
* Reference: https://launchpad.net/~ice3-developers (Luciano Jesus/jesusjpj) &lt;br /&gt;
&lt;br /&gt;
About your project&lt;br /&gt;
&lt;br /&gt;
1. What is the name of your project?&lt;br /&gt;
&lt;br /&gt;
Shortcut Helpers&lt;br /&gt;
&lt;br /&gt;
2. 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?&lt;br /&gt;
&lt;br /&gt;
3. 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&#039;s good to have a plan at the beginning so you have an idea of where you&#039;re headed.) Note that you should probably plan to have something &amp;quot;working and 90% done&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4. 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.&lt;br /&gt;
 	&lt;br /&gt;
My experience developing Simulator Game Wars Tarapaca (which use Python and GTK), how close I am to implement the project with OLPC Sugar (The kids in my province are benefiting from OLPC) and ease of purchase that I have knowledge makes it a potential candidate to complete this project.&lt;br /&gt;
 &lt;br /&gt;
5. What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)&lt;br /&gt;
&lt;br /&gt;
medium&lt;br /&gt;
&lt;br /&gt;
6. Describe a great learning experience you had as a child.&lt;br /&gt;
&lt;br /&gt;
7. 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?&lt;br /&gt;
&lt;br /&gt;
The children in my country and especially my department are among the beneficiaries of this project so I would put my bit and bring more functionality to Sugar for children to be more efficient with the use of this tool. That will be an additional stimulus for me.&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Oficina&amp;diff=25300</id>
		<title>Oficina</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Oficina&amp;diff=25300"/>
		<updated>2009-04-03T21:55:26Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== About you ===&lt;br /&gt;
&lt;br /&gt;
1. &#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Nathalia Sautchuk Patrício.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
2. &#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My email address is nathalia.sautchuk AT gmail DOT com.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
3. &#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My Sugar Labs wiki username is nathalia.sautchuk.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
4. &#039;&#039;&#039;What is your IRC nickname?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My IRC nickname is nathalia.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
5. &#039;&#039;&#039;What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you&#039;d prefer.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My native language is Portuguese but I have an advanced level of English too.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
6. &#039;&#039;&#039;Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I am located in São Paulo, Brazil (GMT -3). I prefer to work after the lunch time until late hours in the night but it is not a problem to work in other periods.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
7. &#039;&#039;&#039;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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Yes, I participated in some open-source projects before. Some of them were developed in university classes (they are in different stages of development) and they are hosted at Google Code:&lt;br /&gt;
&lt;br /&gt;
* Alumini (http://code.google.com/p/alumini/): a conferences manager;&lt;br /&gt;
* Labsof2 (http://code.google.com/p/labsoft2/): a System Service Center and&lt;br /&gt;
* Pintassilgo (http://code.google.com/p/pintassilgo/): an image gallery.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I participated in other open-source projects when I was an intern at LSI-USP (Integrated Systems Laboratory at University of São Paulo):&lt;br /&gt;
* Jogo do piano (http://code.google.com/p/jogodopiano/): a music game for XO and&lt;br /&gt;
* Oficina (http://code.google.com/p/oficina/): a paint activity for XO (later incorporated as official activity in builds).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have just started two new open-source projects at university:&lt;br /&gt;
* Labsoftinfra (http://code.google.com/p/labsoftinfra/): an application for PDA to manage the classroom equipments and a web application to supervise the university stock. It has been developed for a course named Software Engineering Laboratory 2 and&lt;br /&gt;
* FEBRACEV (http://github.com/nathaliaspatricio/febracev): my capstone project and it will be a Virtual Science Fair.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The main open-source project that I have participated was the development of Oficina (Paint Activity) for Sugar: http://dev.laptop.org/git/projects/oficina. I developed this project for about six months (between 2007 April and 2007 September). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
My profile pages for those projects are:&lt;br /&gt;
&lt;br /&gt;
* Google Code: http://code.google.com/u/nathalia.sautchuk/ and&lt;br /&gt;
* GitHub: http://github.com/nathaliaspatricio.&lt;br /&gt;
&lt;br /&gt;
=== About your project ===&lt;br /&gt;
&lt;br /&gt;
1. &#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The name of my project is “ Programmable Brushes for Oficina”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
2. &#039;&#039;&#039;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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Oficina is one of the Paint Activities for Sugar. It has a lot of tools like brushes, eraser, forms and text. The objective is refactoring the Oficina code and make a common base where tools can be plugged. The current available tools will use this base. With this, kids can put the tools that they want, including their own brushes. &lt;br /&gt;
&lt;br /&gt;
In Turtle Art Activity there already is a way to plug a python code to add new block&#039;s functions. The idea is add a similar feature to Oficina. Sugar has already a python editor called Pippy. Using this kids can developed or edit your own brush and import your custom code into Oficina using the Pippy button.&lt;br /&gt;
&lt;br /&gt;
One example of a tool code (nowadays it is the current brush):&lt;br /&gt;
&lt;br /&gt;
    def brush(self, widget, coords, last, size = 5, shape = &#039;circle&#039;):&lt;br /&gt;
        widget.desenha = False&lt;br /&gt;
        if(shape == &#039;circle&#039;):&lt;br /&gt;
            widget.pixmap.draw_arc(widget.gc_brush, True, coords[0], coords[1], size, size, 0, 360*64)&lt;br /&gt;
            if last:&lt;br /&gt;
                widget.gc_brush.set_line_attributes(size, gtk.gdk.LINE_SOLID, gtk.gdk.CAP_ROUND, gtk.gdk.JOIN_ROUND)&lt;br /&gt;
                widget.pixmap.draw_line(widget.gc_brush,last[0]+size/2,last[1]+size/2,coords[0]+size/2,coords[1]+size/2)&lt;br /&gt;
                widget.gc_brush.set_line_attributes(0, gtk.gdk.LINE_SOLID, gtk.gdk.CAP_ROUND, gtk.gdk.JOIN_ROUND)&lt;br /&gt;
        if(shape == &#039;square&#039;):&lt;br /&gt;
            widget.pixmap.draw_rectangle(widget.gc_brush, True, coords[0], coords[1], size, size)&lt;br /&gt;
            if last:&lt;br /&gt;
                points = [coords, last, (last[0]+size,last[1]+size), (coords[0]+size,coords[1]+size)]&lt;br /&gt;
                widget.pixmap.draw_polygon(widget.gc_brush,True,points)&lt;br /&gt;
                points = [(last[0]+size,last[1]), (coords[0]+size,coords[1]), (coords[0],coords[1]+size), (last[0],last[1]+size)]&lt;br /&gt;
                widget.pixmap.draw_polygon(widget.gc_brush,True,points)&lt;br /&gt;
        if last:&lt;br /&gt;
            x = min(coords[0], last[0])&lt;br /&gt;
            width = max(coords[0], last[0]) - x&lt;br /&gt;
            y = min(coords[1], last[1])&lt;br /&gt;
            height = max(coords[1], last[1]) - y&lt;br /&gt;
            widget.queue_draw_area(x, y, width+size, height+size) # We add size to avoid drawing dotted lines&lt;br /&gt;
        else:&lt;br /&gt;
            widget.queue_draw()&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Other important functionality is that children can share their brushes since Sugar 0.84 already allows users to take any item in the Journal and send it to anyone else. There are already some available tools for default but kids can modify or delete this.&lt;br /&gt;
&lt;br /&gt;
Oficina is developed in Python using PyGTK library and the bucket tool is implemented in C language. I will use these technologies in my project.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
3. &#039;&#039;&#039;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&#039;s good to have a plan at the beginning so you have an idea of where you&#039;re headed.) Note that you should probably plan to have something &amp;quot;working and 90% done&amp;quot; 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.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My initial planning to develop the project is:&lt;br /&gt;
&lt;br /&gt;
May 23 - June 5&lt;br /&gt;
* Study the Oficina code and his architecture (remember some things because it has a lot of time since I worked with it)&lt;br /&gt;
* Study a similar feature in the Turtle Art Activity&lt;br /&gt;
&lt;br /&gt;
June 6 - July 7&lt;br /&gt;
* Development of the common base&lt;br /&gt;
&lt;br /&gt;
July 8 - July 12&lt;br /&gt;
* Preparation of the alpha release&lt;br /&gt;
* Development of some example brushes for demonstration&lt;br /&gt;
&lt;br /&gt;
July 13&lt;br /&gt;
* Mid term evaluation&lt;br /&gt;
* Release the alpha version&lt;br /&gt;
&lt;br /&gt;
July 14 - July 23&lt;br /&gt;
* Tests on XO&lt;br /&gt;
* Ask for bugs and improvements in community&lt;br /&gt;
&lt;br /&gt;
July 24 - August 3&lt;br /&gt;
* Correction of the bugs&lt;br /&gt;
&lt;br /&gt;
August 4 - August 13&lt;br /&gt;
* Ask for feedback about the correction activity&lt;br /&gt;
* Preparation for the beta version release&lt;br /&gt;
&lt;br /&gt;
August 14 - August 22&lt;br /&gt;
* Release the beta version&lt;br /&gt;
&lt;br /&gt;
This is rough plan to the work. I like Agile methodologies and I will reschedule the activities when it is necessary.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
4. &#039;&#039;&#039;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.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The main open-source project that I have participated was the development of Oficina (Paint Activity) for Sugar: http://dev.laptop.org/git/projects/oficina. Because of that I have a good knowledge about the activity, the language Python and the library PyGTK (that will be used in the project). Moreover, I already know the process of developing a open-source project and in particular the process adopted by Sugar Labs. Yet I know how to use the tools like Git and Trac (that it can be used in the project) and I participe in the Sugar Labs lists (iaep@lists.sugarlabs.org, devel@lists.sugarlabs.org) for some time.I have a good base in software engineering since I have studied this at university and I am in the fifth year (the last year of undergraduation course). I have a good experience at software development (with different languages and technologies) since I work in the area for over 3 years.&lt;br /&gt;
&lt;br /&gt;
=== You and the community ===&lt;br /&gt;
&lt;br /&gt;
1. &#039;&#039;&#039;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.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My answer:&lt;br /&gt;
&lt;br /&gt;
This project is important for Sugar Labs community since a Paint Activity like Oficina is one of the core activities in the Sugar and it has a good and improved activity of this type is necessary for the adoption by schools and kids. Before children can read words they learn another expression ways and the painting is one of the most important way. In my proposal the main idea is to turn Oficina a more flexible expression environment. This would allow greater freedom for children&#039; expression since they could create their own brushes. Moreover, this idea has a interdisciplinary characteristic because children can work the artistic side and also learn how to programming. When I participated in deployment of XO here in Brazil we had a couple of discussions on what the children wanted and what we didn&#039;t have. I thought they needed more brushes and tools. Especially, the power to create them on our own, which is missing.&lt;br /&gt;
&lt;br /&gt;
Manu Sheel Gupta (manu@laptop.org) - Oficina maintainer:&lt;br /&gt;
&lt;br /&gt;
This project will help meet one of the most important goals of Sugar Labs and free software - &amp;quot;to make it simple for the user to extend activities&amp;quot;. This is very important as free software communities build on top of each others&#039; work to build learning eco-systems. Collaboration, and building of such an eco-system in absolutely essential for the sustainability of the project and the communities. I believe that giving the power to the user to develop brushes of their choice is what a paint activity is supposed to do. And, this feature will help shape this idea, and put it in the right context, which has been missing since day one of any paint project. I wish to see this proposal getting selected.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
2. &#039;&#039;&#039;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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Yes. In 2007 I was an intern at LSI-USP (Integrated Systems Laboratory at University of São Paulo) and I worked at UCA project (In english One Computer per Student) sponsored by the Brazilian Federal Government. In this project the laboratory was responsible for a pilot in a school at São Paulo testing the XO netbooks. I followed what happened in the pilot of this school because sometimes I had to go there. So I have a close contact with people that works at this school and I suggest to deploy there because teachers have experience in projects like that.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
3. &#039;&#039;&#039;What will you do if you get stuck on your project and your mentor isn&#039;t around?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If I get stuck on my project I will try to find the solutions on the internet (in some site, blog or forum). If this does not work I will ask someone in the Sugar IRC channel. If anyone can not help me I will ask in some discussion lists like the Sugar Labs lists or Python lists. If anything works I will send an e-mail requesting a help for my mentor before the planned meeting.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
4. &#039;&#039;&#039;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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I will create a page about Oficina in the Sugar Labs wiki that I intend to put the status of project. Also I will post frequently in a blog that I can create for the project and in my current blog (http://nathaliapatricio.blogspot.com). If I have any problems over the course of the project I will try to find the solutions on the internet (in some site, blog or forum). If this does not work I will ask someone in the Sugar IRC channel. If anyone can help me I will ask in some discussion lists like the Sugar Labs lists or Python list&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
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&#039;s email address in place of the word &amp;quot;Restart&amp;quot; - your screenshot should contain your email instead.&lt;br /&gt;
&lt;br /&gt;
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&#039;s email address in place of the word &amp;quot;Restart&amp;quot; - your screenshot should contain your email instead.&lt;br /&gt;
&lt;br /&gt;
1. &#039;&#039;&#039;We want to make sure that you can set up a 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 &amp;quot;Restart.&amp;quot; See the image on the right for an example. It&#039;s normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
2. &#039;&#039;&#039;What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My T-Shirt size is Medium.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
3. &#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A great learning experience came from the incentive of reading Brazilian Children&#039;s books when I was in primary school. Nowadays I can learn about everything that I want or which I am curious about. I think it is possible today because of this incentive that I have had. This makes me more participative in my learning process and interested in learning technologies.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
4. &#039;&#039;&#039;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?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When I was working at LSI-USP with XO netbooks I (and another people of the team) did a initial usability study of Oficina with some kids. We had an short paper published in 2008 about that at IEEE ICALT (IEEE International Conference on Advanced Learning Technologies).&lt;br /&gt;
&lt;br /&gt;
The paper calls &amp;quot;Testing the OLPC Drawing Activity: an usability report&amp;quot; by Alexandre Antonino Gonçalves Martinazzo, Nathalia Sautchuk Patrício, Leandro Coletto Biazon, Irene Karaguilla Ficheman and Roseli de Deus Lopes. It is available in the link: http://www2.computer.org/portal/web/csdl/doi/10.1109/ICALT.2008.200.&lt;br /&gt;
&lt;br /&gt;
[[Category:gsoc]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Talk:Oficina&amp;diff=25299</id>
		<title>Talk:Oficina</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Talk:Oficina&amp;diff=25299"/>
		<updated>2009-04-03T21:54:48Z</updated>

		<summary type="html">&lt;p&gt;Homunq: New page: I&amp;#039;m very sorry, we cannot consider this application because you did not submit it on Google&amp;#039;s web application before the deadline. I made every attempt to let students know this, I&amp;#039;m reall...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I&#039;m very sorry, we cannot consider this application because you did not submit it on Google&#039;s web application before the deadline. I made every attempt to let students know this, I&#039;m really sorry if you did not get the word. [[User:Homunq|Homunq]] 21:54, 3 April 2009 (UTC)&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Talk:KDEEdu&amp;diff=25081</id>
		<title>Talk:KDEEdu</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Talk:KDEEdu&amp;diff=25081"/>
		<updated>2009-04-03T15:48:44Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* Please be more specific */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First off, thanks for making the effort; your proposal is interesting, and it would be great for Sugar if you can accomplish your underlying goal. &lt;br /&gt;
&lt;br /&gt;
However, I am not an expert on gtk/qt issues, but honestly I think that idea, as you present it, is a bit of a stretch. If you want this proposal to be ready by the deadline, you will have to devote some real time to hanging out on IRC and getting help with it. As a start, I think you should consider including QT in the activity itself. It is AFAICT around 20 MB of bloat, which is unfortunate, but it will get you there so much faster. So your project would be something like&lt;br /&gt;
&lt;br /&gt;
1. get qt to work without a package manager, from inside activity directory&lt;br /&gt;
&lt;br /&gt;
2. use qgtkstyle to get it to look superficially sugary&lt;br /&gt;
&lt;br /&gt;
3. reprogram it to be compatible with sugar - toolbar, rainbow security, autosave, dbus, etc. This is the real work of sugarizing. It is better if you can avoid forking the application - if it provides its interface via widgets which you can rearrange via another layer you put above. You would have to research whether this is possible.&lt;br /&gt;
&lt;br /&gt;
4. document the above so it&#039;s easy to do with other kdeedu activities. &lt;br /&gt;
&lt;br /&gt;
5. (optional) It would be cool if you could figure out some strategy to avoid repeatedly downloading 20MB of QT, yet still rely on just .xo packages without real package or dependency management.&lt;br /&gt;
&lt;br /&gt;
Steps 1 and 2 should be relatively simple. I have no good idea how hard step 3 would be.&lt;br /&gt;
&lt;br /&gt;
Again, unless you pester the sugar-devel mailing list and/or IRC, your proposal will probably not be ready in time. If you do do so, you may want to keep an open mind and ask about exploring other project ideas, either instead of this one or in addition to it; though you will have to decide relatively quickly, as you do not have a lot of time to get a proposal (or proposals) into shape.&lt;br /&gt;
&lt;br /&gt;
[[User:Homunq|Homunq]] 18:23, 31 March 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Please be more specific ==&lt;br /&gt;
&lt;br /&gt;
Talk about some of the specific UI choices, and any changes in save behavior, to make your app fit into sugar. Include some of this analysis in your schedule - when would you imagine you&#039;d be working on what?&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Talk:Summer_of_Code/2009/Groupthink&amp;diff=24970</id>
		<title>Talk:Summer of Code/2009/Groupthink</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Talk:Summer_of_Code/2009/Groupthink&amp;diff=24970"/>
		<updated>2009-04-03T06:06:49Z</updated>

		<summary type="html">&lt;p&gt;Homunq: New page: OK, well, I&amp;#039;m drunk at the moment, so don&amp;#039;t expect a lot of coherence. But the point I want to make is that, you&amp;#039;ve heard me say it before, I think that the sync/async collaboration, the d...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;OK, well, I&#039;m drunk at the moment, so don&#039;t expect a lot of coherence. But the point I want to make is that, you&#039;ve heard me say it before, I think that the sync/async collaboration, the differential versioned filesytem, and the undo stack, is really the same issue. If you can make a network protocol that does three-way diffs using the same data that is in the versioned filesystem, and keeps XML compliant to the DTD, anyone can use it for any data and they get versioning, collaboration, and undo/redo for free and sugar rules the world. [[User:Homunq|Homunq]] 06:06, 3 April 2009 (UTC)&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=KDEEdu&amp;diff=24949</id>
		<title>KDEEdu</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=KDEEdu&amp;diff=24949"/>
		<updated>2009-04-03T02:51:29Z</updated>

		<summary type="html">&lt;p&gt;Homunq: /* You and the community */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please apply also in [http://socghop.appspot.com melange, google&#039;s web app]; if you do not apply there &#039;&#039;&#039;before&#039;&#039;&#039; April 3, we will not be able to accept your application. Also, use the &amp;quot;discussion&amp;quot; link above to see our questions/suggestions for you. (If you want to get email when we change that, you can use &amp;quot;prefs&amp;quot; and &amp;quot;watch&amp;quot; above).&lt;br /&gt;
&lt;br /&gt;
{{TOCright}}&lt;br /&gt;
&lt;br /&gt;
====About you====&lt;br /&gt;
&lt;br /&gt;
* What is your name?&lt;br /&gt;
Yazen Ghannam&lt;br /&gt;
* What is your email address?&lt;br /&gt;
yghannam7388@gmail.com&lt;br /&gt;
* What is your Sugar Labs wiki username?&lt;br /&gt;
yghannam7388&lt;br /&gt;
* What is your IRC nickname?&lt;br /&gt;
yghannam7388&lt;br /&gt;
* What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you&#039;d prefer.)&lt;br /&gt;
English&lt;br /&gt;
* Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)&lt;br /&gt;
Orlando, Florida, USA. GMT -4 &lt;br /&gt;
&lt;br /&gt;
I can work in the mornings or evenings, from 7am to 2pm or from 5pm to 11pm.&lt;br /&gt;
* 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?&lt;br /&gt;
I am a new member of the Ubuntu Bugsquad.&lt;br /&gt;
https://launchpad.net/~yghannam7388&lt;br /&gt;
&lt;br /&gt;
====About your project====&lt;br /&gt;
&lt;br /&gt;
* What is the name of your project?&lt;br /&gt;
KDEEdu&lt;br /&gt;
* 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?&lt;br /&gt;
There are a number of educational applications available on the K Desktop Environment. Sugar, having education in mind, would like to use these applications. The only problem is that these applications   are written for KDE using the Qt toolkit, while Sugar uses the GTK+ toolkit. Therefore for Sugar to have access to these applications they must be rewritten using the GTK+ toolkit.&lt;br /&gt;
&lt;br /&gt;
Trolltech, the developer of the Qt Toolkit, has included QGtkStyle into Qt 4.5. The QGtkStyle class provides a widget style rendered by GTK+ (http://doc.trolltech.com/4.5/qgtkstyle.html). QGtkStyle will allow programs written in Qt to integrate better into desktop environments that use GTK+. Using QGtkStyle as an alternative to recoding an entire program from Qt to GTK+ will dramatically speed up the process of bringing KDEEdu applications to Sugar. &lt;br /&gt;
&lt;br /&gt;
The only drawback to using QGtkStyle is that the Qt libraries will still be needed to run KDEEdu applications on Sugar. This may pose a problem for hardware with less resources such as the OLPC XO-1. After porting a KDEEdu application to Sugar and finding it stable, I will try to reduce the number of Qt libraries by removing ones that are not needed by the application.&lt;br /&gt;
&lt;br /&gt;
One experience that was lacking in my early education was the use of computers to solve math problems. You could always use a word processor to type a report or the internet to find a map for geography but you always needed to solve math problems out my hand. Therefore, I would like to &amp;quot;sugarize&amp;quot; a mathematics application from KDEEdu, probably KAlgebra since it is general purpose and has graphing capabilites. I believe this will help all students, but especially those who may find it hard to visualize math concepts.&lt;br /&gt;
&lt;br /&gt;
* 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&#039;s good to have a plan at the beginning so you have an idea of where you&#039;re headed.) Note that you should probably plan to have something &amp;quot;working and 90% done&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
May 23 Start Work; Add QGtkSyle to KDEEdu application. &lt;br /&gt;
&lt;br /&gt;
May 30&lt;br /&gt;
Begin to &amp;quot;Sugarize&amp;quot; the application. This entails making the application compatible with Sugar and its features. &lt;br /&gt;
&lt;br /&gt;
June 6&lt;br /&gt;
Continue &amp;quot;Sugarizing&amp;quot;/debugging&lt;br /&gt;
&lt;br /&gt;
June 13&lt;br /&gt;
Continue &amp;quot;Sugarizing&amp;quot;/debugging&lt;br /&gt;
&lt;br /&gt;
June 20&lt;br /&gt;
Finish &amp;quot;Sugarizing&amp;quot;/debugging&lt;br /&gt;
&lt;br /&gt;
June 27&lt;br /&gt;
Package Application and dependencies/test on various platforms&lt;br /&gt;
&lt;br /&gt;
July 6-13 Midterm Evaluation&lt;br /&gt;
&lt;br /&gt;
July 13&lt;br /&gt;
Begin reducing Qt library/debugging&lt;br /&gt;
&lt;br /&gt;
July 20&lt;br /&gt;
Finish reducing Qt library/debugging&lt;br /&gt;
&lt;br /&gt;
July 27 &lt;br /&gt;
Package Application and dependencies/test on various platforms&lt;br /&gt;
&lt;br /&gt;
August 3&lt;br /&gt;
Organize and proofread documentation&lt;br /&gt;
&lt;br /&gt;
August 10 End Work&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
This summer I will change my major from Electrical Engineering to Computer Engineering. The change is happening due to my increased interest in programming and open source software. My interest in software started when I took an introductory course on C programming. In this course I successfully developed programs to act as automatic teller machines, inventory databases, etc. I came to realize how useful programming knowledge is in our time. Later in my school career I took a course on Computer Organization. This course was based more on hardware but we used programming to understand the concepts. Our project for this course was to develop a program to act as a MIPS processor emulator; this emulator needed to successful process different instructions based on the MIPS datapath given to us. This would be my first experience with a large and complex program.&lt;br /&gt;
&lt;br /&gt;
Eventually, I realized that most of my programming knowledge is based on developing engineering/scientific command line applications. So earlier this year I set a goal for myself to learn to use graphical toolkits. In order to learn the two major toolkits used in my experience, Qt and GTK+, I decided to help port applications between the two toolkits. This was to become my summer project, until I heard about Google Summer of Code and the KDEEdu idea from SugarLabs. &lt;br /&gt;
&lt;br /&gt;
I have already decided to dedicate myself to learning the skills needed for this idea over the summer. Nonetheless, I feel that working in a structured way with professionals would be extremely beneficial. My dedication to learning these skills and help from my mentor and the community will make success for this project a reality.&lt;br /&gt;
&lt;br /&gt;
====You and the community====&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
With the completion of this project, Sugar Labs will have a documented procedure to port and deploy applications that are part of the KDE Education Project. This will include about twenty applications, and others that are built using Qt but are not part of KDEEdu. This will save Sugar activity developers from having to write applications that may already exist but are not built for Sugar or that use GTK+. &lt;br /&gt;
&lt;br /&gt;
From homunq: KDEEdu is one of the most important set of open source educational programs. Having a demonstrated way to get those working in Sugar would help fill a number of important holes in our activity line-up, and would also help with making impressive demos.&lt;br /&gt;
&lt;br /&gt;
* 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?&lt;br /&gt;
&lt;br /&gt;
I live in large metropolitan area with a school district that is making large budget cuts. The best way to deploy Sugar in the area would be to contact Orange County Schools, the local school district, and offer to setup Sugar on computers within one of the local schools. Hopefully, in the end, the local district will see benefit in switching all of its student-used computers to Sugar or another open source system. I could contact a local school if Sugar Labs is willing to deploy in my area.&lt;br /&gt;
&lt;br /&gt;
* What will you do if you get stuck on your project and your mentor isn&#039;t around?&lt;br /&gt;
&lt;br /&gt;
I would look for answers with other developers. This project is a crossroads of many greater projects (Sugar, KDE, Qt, GTK+) and so I will attempt to get answers any way I can. That includes the fundamental Google search, followed by contacting developers on IRC and mailing lists. This task of inter-compatibility between graphical toolkits is so important to open source development that there should be some great advice available.&lt;br /&gt;
&lt;br /&gt;
* 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?&lt;br /&gt;
&lt;br /&gt;
I will be active on the IRC channels and mailing lists. If possible, I&#039;ll create a blog page and link it to one of the mailing lists or RSS feeds. This way I can post on my progress everyday (or more) and everyone will be able to follow.&lt;br /&gt;
&lt;br /&gt;
====Miscellaneous====&lt;br /&gt;
* 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 &amp;quot;Restart.&amp;quot; See the image on the right for an example. It&#039;s normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.&lt;br /&gt;
[[Image:Yazen&#039;sDevSkillz.png|300px]]&lt;br /&gt;
* What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)&lt;br /&gt;
Large&lt;br /&gt;
* Describe a great learning experience you had as a child.&lt;br /&gt;
I have always enjoyed hand-ons learning. One experience that I enjoy was making ice cream in school. The process was very simple: take the ingredients (milk, sugar, flavoring, salt) and put it all in a plastic bag. Next place the bag in a coffee can filled with ice. Now roll the can on the table (or wherever) for a while, maybe it was half an hour to an hour. Eventually, the ingredients in the bag will solidify and you will have ice cream. I think this was the first time that was able to see and participate in the process of making something I loved. &lt;br /&gt;
* 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?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Category:2009 GSoC applications]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:GSoC]]&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Talk:Interactive_Worksheets&amp;diff=24904</id>
		<title>Talk:Interactive Worksheets</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Talk:Interactive_Worksheets&amp;diff=24904"/>
		<updated>2009-04-02T18:18:25Z</updated>

		<summary type="html">&lt;p&gt;Homunq: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How would your proposal differ from just packaging a web view of a locally-run copy of Sage, as a sugar activity? (If the answer is &amp;quot;not at all&amp;quot;, that&#039;s fine, but you should say that.) [[User:Homunq|Homunq]] 21:09, 1 April 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
I&#039;ll take a look at Sage. Maybe I should be thinking about working with them instead. [[User:Mabbikeel|mabbikeel]] 22:05, 1 April 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
OK, but they&#039;re heavy-duty math folks. I doubt that sugarizing is a priority for them, it could be for us if you convinced us it would be a good experience for kids. Sage is awesome, btw. [[User:Homunq|Homunq]] 18:17, 2 April 2009 (UTC)&lt;/div&gt;</summary>
		<author><name>Homunq</name></author>
	</entry>
</feed>