<?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=Mohayon</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=Mohayon"/>
	<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/go/Special:Contributions/Mohayon"/>
	<updated>2026-04-16T15:50:51Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=User:Rishabhnambia&amp;diff=104810</id>
		<title>User:Rishabhnambia</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=User:Rishabhnambia&amp;diff=104810"/>
		<updated>2026-04-08T13:21:19Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: email redacted&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Sugarizer School Box - GSoC &#039;18  =&lt;br /&gt;
&lt;br /&gt;
== About Me ==&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Name:&#039;&#039;&#039; Rishabh Nambiar&lt;br /&gt;
:&#039;&#039;&#039;Email:&#039;&#039;&#039; [mailto:rishabhn@protonmail.com rishabhn@protonmail.com]&lt;br /&gt;
:&#039;&#039;&#039;Sugar Labs wiki username:&#039;&#039;&#039; Rishabhnambia&lt;br /&gt;
:&#039;&#039;&#039;IRC nickname:&#039;&#039;&#039; rishabhnambiar&lt;br /&gt;
:&#039;&#039;&#039;Github:&#039;&#039;&#039; https://github.com/rishabhnambiar&lt;br /&gt;
:&#039;&#039;&#039;Languages:&#039;&#039;&#039; English&lt;br /&gt;
:&#039;&#039;&#039;Where am I located? and what hours(UTC) do I tend to work?&#039;&#039;&#039;&lt;br /&gt;
: I&#039;m located in Mumbai, India (UTC +05:30).&lt;br /&gt;
: Work Hours: 5:00 AM to 1:00 PM UTC&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Past experiences with Open-Source projects:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: I have worked with an open-source organization called [https://github.com/frappe ERPNext] sporadically between 2016 and 2017 as a part of their Developer Operations team.&lt;br /&gt;
 &lt;br /&gt;
::* I added an AWS S3 Integration to Frappe, a Python framework that powers ERPNext.&lt;br /&gt;
::* https://github.com/frappe/frappe/pull/4272&lt;br /&gt;
::* Here’s a PR I made that has some Ansible:&lt;br /&gt;
::* https://github.com/frappe/bench/pull/473/&lt;br /&gt;
: I&#039;ve been making minor contributions since May 2016.&lt;br /&gt;
&lt;br /&gt;
::*https://github.com/frappe/bench/pull/473 [Ansible]&lt;br /&gt;
::*https://github.com/coding-blocks/content-downloader/pull/7 [Python]&lt;br /&gt;
::*https://github.com/fossasia/meilix-generator/pull/110 [HTML, CSS, JavaScript]&lt;br /&gt;
&lt;br /&gt;
=Project Description =&lt;br /&gt;
&lt;br /&gt;
:&lt;br /&gt;
[[File:Sugarizerschoolbox diagram.png|center|flow]]&lt;br /&gt;
:&lt;br /&gt;
&lt;br /&gt;
==== Goal #1: Sugarizer Raspberry Pi Images with build scripts ====&lt;br /&gt;
:&lt;br /&gt;
:The first goal is to create a Raspberry Pi image and build scripts based on Raspbian that can serve Sugarizer to a classroom full of students. &lt;br /&gt;
&lt;br /&gt;
:On booting, the Raspberry Pi will:&lt;br /&gt;
:*act as a WiFi AP that clients(browsers, sugarizer apps) can connect to.&lt;br /&gt;
:*serve Sugarizer using Sugarizer-server on the local WiFi so there will be no requirement for Internet connectivity for now.&lt;br /&gt;
:*start a browser session running Sugarizer client so a single user/instructor can use it by connecting a display to the Pi.&lt;br /&gt;
&lt;br /&gt;
:This is being created because the Raspberry Pi is inexpensive, widely available and many such Sugarizer School Boxes can provide a cost-effective way of reaching out to more students and communities through Sugar. &lt;br /&gt;
&lt;br /&gt;
:Improvements to the Internet-In-A-Box [https://github.com/iiab/iiab/tree/master/roles/sugarizer Ansible playbook] for Sugarizer will also be made in this section. &lt;br /&gt;
:This will include making sure that the IIAB playbook uses the latest version of sugarizer with all available functionality and ensuring that it works.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Collaboration &amp;amp; Testing&#039;&#039;&#039;&lt;br /&gt;
:Sugarizer already works really well when deployed locally on a Raspberry Pi and Neighbourhood view is also functional. &lt;br /&gt;
:*On completion of Goal #1, the image build will be tested at real Sugarizer deployments with the help of the community.&lt;br /&gt;
&lt;br /&gt;
====Goal #2: Heroku Button====&lt;br /&gt;
&lt;br /&gt;
:&lt;br /&gt;
[[File:Herokubuttonreadmeexample.png|center]]&lt;br /&gt;
:::::::::::::::::::&#039;&#039;&amp;lt;small&amp;gt;Fig. mockup for a Heroku Button in README.md&amp;lt;/small&amp;gt;&#039;&#039;&lt;br /&gt;
:The second goal is to simplify the way to deploy Sugarizer in the cloud. The priority in this section is get a [https://blog.heroku.com/heroku-button Heroku Button] for sugarizer up and running.&lt;br /&gt;
:&lt;br /&gt;
:A Heroku Button is a simple HTML or Markdown snippet that can be added to READMEs. Clicking a Heroku Button will take you through a guided process to configure and deploy an app running the source code referenced by the button.&lt;br /&gt;
&lt;br /&gt;
:This is being done to provide users a simple, one-click and hassle-free deployment method that will let anyone set up their own instance of Sugarizer without opening a terminal window.&lt;br /&gt;
:&lt;br /&gt;
&lt;br /&gt;
=====Minimum Deliverables=====&lt;br /&gt;
&lt;br /&gt;
:The community has suggested that I should treat improving the Sugarizer School Box as Goal #1 and the deployment scripts as Goal #2. I will start working on the deployment scripts only when Goal #1 is complete.&amp;lt;br&amp;gt;As 90% of the project should ideally be complete by the 2nd Evaluation phase, the Raspberry Pi build, the improved IIAB installer and the Heroku Button script will be ready by then.&lt;br /&gt;
=====Best Case Scenario=====&lt;br /&gt;
&lt;br /&gt;
:If things go as per the timeline till the 2nd evaluation phase, I will also be making a Bash + Docker script for sugarizer deployment. Ansible, Terraform or Packer can be added to the script to allow compatibility for different VPS providers. As the Docker build for Sugarizer-server and Ansible installer for IIAB already exist, this will not take long.&lt;br /&gt;
&lt;br /&gt;
=Timeline=&lt;br /&gt;
::{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Week&lt;br /&gt;
|Date(2018)&lt;br /&gt;
|Period&lt;br /&gt;
|Task&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|April 23 - May 13&lt;br /&gt;
|Community Bonding&lt;br /&gt;
|&lt;br /&gt;
*Set up a blog for posting my weekly progress. &lt;br /&gt;
*Discuss and reshape the Timeline after discussion with my mentor(s).&lt;br /&gt;
*Investigate the causes of MongoDB crashes faced by Sugarizer users and formulate a solution.&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|01&lt;br /&gt;
|May 14 - May 21&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Analyze Sugarizer performance on the Raspberry Pi using parameters like file download size for every page/activity, frequency of page visits, processing required per request and seeing how the Pi server behaves in different conditions. &lt;br /&gt;
*Create a Raspbian Image build for the Pi3 that has an Access Point and Sugarizer-Server running on boot. &lt;br /&gt;
*Use &#039;&#039;&#039;hostapd&#039;&#039;&#039; and &#039;&#039;&#039;dnsmasq&#039;&#039;&#039; to create an access point as shown in this [https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md article].&lt;br /&gt;
|-&lt;br /&gt;
|02&lt;br /&gt;
|May 21 - May 28&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Continue to work on Raspbian Image build and test on my Raspberry Pi 3. &lt;br /&gt;
*This project will involve writing some bash for the build and I’ll use these resources for inspiration:&lt;br /&gt;
&lt;br /&gt;
:*https://github.com/sugarlabs/rpi23-gen-image&lt;br /&gt;
:*https://github.com/iiab/iiab-factory/tree/master/box/rpi&lt;br /&gt;
|-&lt;br /&gt;
|03&lt;br /&gt;
|May 29 - June 04&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Continue to work on the Raspberry Pi image and the build scripts and publish them.&lt;br /&gt;
*Improve the [https://github.com/iiab/iiab/tree/master/roles/sugarizer Ansible playbook] for installing Sugarizer on the Internet-In-A-Box installer. &lt;br /&gt;
*This will include making sure that the IIAB play uses the latest version of sugarizer with all available functionality and ensuring that it works. &lt;br /&gt;
|-&lt;br /&gt;
|04&lt;br /&gt;
|June 05 - June 11&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*On the IIAB Sugarizer install, add safeguards and checks to reduce MongoDB corruption issues caused by incorrect shutdown methods. &lt;br /&gt;
*Study how to make the Sugarizer School Box communicate with the Android and iOS apps.&lt;br /&gt;
*Implement and test on multiple Android devices/tablets.&lt;br /&gt;
|-&lt;br /&gt;
|05&lt;br /&gt;
|June 12 - June 20&lt;br /&gt;
|Phase I Evaluation&lt;br /&gt;
|&lt;br /&gt;
*Formulate a robust upgrade process to ensure that Sugarizer updates are installed successfully without losing any data to instances that have been deployed.&lt;br /&gt;
*Explore [https://github.com/Unitech/pm2 pm2] as a solution to do solve this or use other features of pm2 to enhance reliability.&lt;br /&gt;
:*The aim is to remove the possibility of data loss during after updates.&lt;br /&gt;
|-&lt;br /&gt;
|06&lt;br /&gt;
|June 21 - June 29 &lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Generate a Heroku Button for one-click Sugarizer-server deployment. &lt;br /&gt;
*The project should ideally be 90% complete by the end of June. &lt;br /&gt;
*So my goal at this stage is to have a functional Raspberry Pi image build for Sugarizer, significantly improved IIAB Ansible install script and the Heroku Button. &lt;br /&gt;
|-&lt;br /&gt;
|07&lt;br /&gt;
|June 30 - July 08&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Test Heroku Button deployment.&lt;br /&gt;
*Test the Sugarizer School Box Raspberry Pi image at real Sugarizer deployments with the help of the community.&lt;br /&gt;
|-&lt;br /&gt;
|08&lt;br /&gt;
|July 09 - July 13&lt;br /&gt;
|Phase II Evaluation&lt;br /&gt;
|&lt;br /&gt;
*If the Turtle/Music Blocks release is on schedule, I will add it to the Sugarizer Pi Image build.&lt;br /&gt;
*We can use this release as a test for the upgrade processes created in Week 5.&lt;br /&gt;
*Improvements to the upgrade process will be made. &lt;br /&gt;
|-&lt;br /&gt;
|09&lt;br /&gt;
|July 14 - July 20&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Write a Bash + Docker script to deploy Sugarizer-server on a VPS.This will be done the traditional DevOps way using Ansible.&lt;br /&gt;
*The Ansible component will not take much time because a similar play has already been written [https://github.com/iiab/iiab/tree/master/roles/sugarizer here]. &lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|July 21 - July 28&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Continue working on the Bash + Docker script.&lt;br /&gt;
*Use Packer or Terraform on the script to improve compatibility between VPS providers.&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|July 29 - Aug 5&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
*Test deployment options thoroughly on different VPS providers. &lt;br /&gt;
*Take help from the community for testing the scripts on a larger scale.&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|6 Aug - August 14&lt;br /&gt;
|Final Evaluation&lt;br /&gt;
|&lt;br /&gt;
*Keep a final buffer week for added tasks.&lt;br /&gt;
*Prepare final submissions.&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Convince us why you can finish this project ===&lt;br /&gt;
&lt;br /&gt;
:I believe I can complete this project because of my love and fascination for Linux and my previous work experience with Ansible, Docker and Python.&lt;br /&gt;
&lt;br /&gt;
:*I mentioned my experience with an open-source organization called [https://github.com/frappe ERPNext] above.  &lt;br /&gt;
&lt;br /&gt;
:*In the summer of 2016, I worked as a full-time intern for the same organization. I added automated AWS S3 Backups to their in-house deployment tool, [https://frappe.io/blog/development/deployment-for-everyone. Central]. &lt;br /&gt;
:*This included writing Ansible playbooks and Python that would set up automated backups for all their production servers for their enterprise clients. This was NOT an open source contribution but I’m mentioning this here because it is a major reason for my familiarity with Linux and Deployment. &lt;br /&gt;
:*Some presentations depicting my work at ERPNext can be viewed [https://drive.google.com/drive/folders/0B70J3r6c_RnCdUp5MmNPQWlmV00?usp=sharing here].&lt;br /&gt;
&lt;br /&gt;
:*In the summer of 2017, I was at [https://angel.co/cube-consumer-services-1 Cube] as a  Full-Stack Development Intern. Over the summer, I built a Python based (bottle.py) web application that automated a lot of maintenance tasks for the Operations team that included web scraping and API Development. I also containerized the application using Docker and Docker-Compose.&lt;br /&gt;
&lt;br /&gt;
:This is the first time I’m applying for GSoC and Sugar Labs is the only organization I’m applying to because this project is a really good fit for my skill-set.&lt;br /&gt;
&lt;br /&gt;
= The Project and the Community =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*:&#039;&#039;&#039;Rishabh Nambiar&#039;&#039;&#039;&lt;br /&gt;
:: rishabhn@protonmail.com, [https://twitter.com/rish4bhn Twitter]&lt;br /&gt;
&lt;br /&gt;
::If the project is successfully completed, it will provide Sugar Labs a more portable and inexpensive way of deploying Sugarizer. The Raspberry Pi is inexpensive, widely available and Sugarizer School Boxes can provide a cost-effective way of reaching out to more students and communities through Sugar. This method of deployment requires only one Raspberry Pi 3. &lt;br /&gt;
&lt;br /&gt;
::The convenience of using one-click deployment scripts can be instrumental in getting non-developers to using a project and using a Heroku Button is even better when you don’t have to use to a terminal to have your own instance of Sugarizer.&lt;br /&gt;
=== Answers from the Community ===&lt;br /&gt;
:&lt;br /&gt;
*:&#039;&#039;&#039;Michaël Ohayon&#039;&#039;&#039; (Potential GSoC Mentor)&lt;br /&gt;
:: 1) I think that the Pi will be able to handle the load, we won’t have that much kids connected to the same Pi and the networking process is not that heavy.&lt;br /&gt;
::We should try to launch the server in background and display a web browser in foreground. If the load is too high we will see it quickly.&lt;br /&gt;
::2) Yes, you’re right, the Pi should provide a Wifi AP to allow devices to connect. This AP should bring routing from Ethernet if connected.&lt;br /&gt;
::3) Everything is possible, Ansible is a great tool. Combined with Terraform and Packer we should be allowed to deploy things without having troubles handling multiple cloud providers.&lt;br /&gt;
::The installation script could be performed using simple bash and docker.&lt;br /&gt;
::4) I think you can start thinking on your proposal. You can continue to discuss with us to talk about the project but also the community and the impact of that project.&lt;br /&gt;
::5) For the deployment part we have two options that would be nice to have.&lt;br /&gt;
::* a really simple automation like heroku single click deploy (https://blog.heroku.com/heroku-button). &lt;br /&gt;
:::&#039;&#039;&#039;This is the killer feature we should definitely have.&#039;&#039;&#039;&lt;br /&gt;
::* the devops way using tools like Ansible and Terraform and Packer.&lt;br /&gt;
::&#039;&#039;&#039;One major thing for all platforms is to think about the upgrade processes, how can we update the devices/server without losing data.&#039;&#039;&#039;&lt;br /&gt;
:&lt;br /&gt;
*:&#039;&#039;&#039;Tony Anderson&#039;&#039;&#039; - tony_anderson@usa.net - http://schoolserver.org/&lt;br /&gt;
:: This is exactly how the xsce server works so you may get valuable help from that community (xsce or iiab).&lt;br /&gt;
::A continuing issue is performance of the server in a classroom or school. One metric is the number of simultaneous connections the device can support (a classroom of 40-60 is not uncommon). Response time to requests to the server can be limited by the size of memory, the speed of access to the sd card, or the processor speed. I would be very interested in the methodology you propose since that process would apply equally to the schoolserver.&lt;br /&gt;
::One issue is to characterize the workload - how often does a user request a transaction from the server, what is the time between requests (when the user is reading the response to the previous request), how much processing is required for a request (e.g. a text search), how much information is required to satisfy a request (e.g. size of file download). So far as I know no one has attempted this characterization for a classroom. This load could be different for Sugarizer than for Sugar, but the effort would be valuable in any case)&lt;br /&gt;
:&lt;br /&gt;
*:&#039;&#039;&#039;Tim Moody&#039;&#039;&#039; - tim@timmoody.com - http://internet-in-a-box.org/&lt;br /&gt;
::Speaking of reliability, we have experienced a number of occasions when mongodb was corrupt on the rpi, perhaps through disorderly shutdown. Perhaps you can sort that out.&lt;br /&gt;
::I would also recommend focusing on the rpi install before turning to Heroku or AWS as most users are without an internet connection. All I&#039;m suggesting is that you start with Sugarizer School Box item 1 and then proceed to item 2 when it is complete.&lt;br /&gt;
:&lt;br /&gt;
&#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;
:If I get stuck, I will first try my best to find a solution myself (Web Search, StackOverflow). I can ask for help on #sugar or from some friends and ex-colleagues who are Open Source enthusiasts.&lt;br /&gt;
&lt;br /&gt;
&#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;
:In the Community Bonding period, I will create a blog for myself and I will share my weekly experiences, progress and plans for the next week through it.&lt;br /&gt;
:During the coding period, I&#039;ll attend the Development Team Meetings and will also be available on IRC (#sugar) when I&#039;m working.&lt;br /&gt;
&lt;br /&gt;
= Miscellaneous =&lt;br /&gt;
&lt;br /&gt;
====Setting up a Development Environment====&lt;br /&gt;
&lt;br /&gt;
:I wasn’t sure if this project falls under the Sugar-Desktop projects or the Sugar Web projects so for a relevant screening task, you can check a Sugarizer deployment I’ve done at http://rishabhn.xyz:8080/&lt;br /&gt;
&lt;br /&gt;
:I&#039;ve deployed Sugarizer on my Raspberry Pi 3 and a VPS with Docker and without it.&lt;br /&gt;
:It works really well and I haven’t run into any major issues.&lt;br /&gt;
&lt;br /&gt;
====Tell us something about yourself that will make us like you more.====&lt;br /&gt;
:*I believe I’m a good candidate for this project because I’m an avid distro-hopper. The process of merely installing new Linux distributions and setting them up the way I like takes a large chunk of my time. So, the Sugarizer School Box isn’t just some project I’d like to do for GSoC, it’s something I’ll actually enjoy building!&lt;br /&gt;
:*I come from a family of musicians so I’ve turned into an amateur singer and guitar player as I’ve grown up. I also know my way around recording instruments and vocals. If the Sugarizer School Box project didn’t exist, I would have picked a Music Blocks project for sure. Maybe I can work on it sometime in the future! &lt;br /&gt;
&lt;br /&gt;
====Describe a great learning experience you had as a child.====&lt;br /&gt;
&lt;br /&gt;
:Well, the most significant learning experience I can recollect is when I learned how to “learn”.&lt;br /&gt;
:This is something entirely personal as different individuals require different learning methods.&lt;br /&gt;
:I don’t remember exactly when or how I found out but I finally realized that I can learn only by “doing” and not by reading or writing about concepts.&lt;br /&gt;
&lt;br /&gt;
:Now, I just use that concept to try learning whatever I need to. It’s all about getting your hands dirty and putting in the work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:2018 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=104809</id>
		<title>Summer of Code/2015/mohayon.SugarWebBasicActivitySet</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=104809"/>
		<updated>2026-04-08T13:20:15Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: email redacted&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About You ==&lt;br /&gt;
&#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Michaël Ohayon, I am a 4th year student at Epitech Paris&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your IRC nickname on irc.freenode.net?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your first 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 French, I am fluent in English.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where are you located, and what hours (UTC) 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&#039;m located in Paris, France.&lt;br /&gt;
&lt;br /&gt;
I&#039;m planning to work 17:00 - 22:00 on Monday, Tuesday and Wednesday (I got a part time job) and 10:00 - 18:00 the other days.&lt;br /&gt;
&lt;br /&gt;
&#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;
I got invested inside the french ubuntu loco team (ubuntu-fr.org) by helping during ubuntu parties.I started in October 2007 as a simple visitor and became a volunteer by helping people switching from Windows to Ubuntu.&lt;br /&gt;
Back in thoses days, migrating was not as simple as today and this was a really great human experience for me. As a longtime GNU/Linux educated user, Open-source is something really important to me. It&#039;s a way to communicate and share values with everyone.&lt;br /&gt;
&lt;br /&gt;
Now that I&#039;m a programmer, I think that I can move forward and also contribute with my programming skills.&lt;br /&gt;
&lt;br /&gt;
I attended a GSOC conference by Lionel Laské and decided to register.&lt;br /&gt;
&lt;br /&gt;
==About your project==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugar Web Basic Activity Set&lt;br /&gt;
&lt;br /&gt;
&#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? What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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;
This project is a full rewriting of some Sugar apps : Calculate, Paint, Memorize and Record using the Sugar Web Framework in order to get close to every device.&lt;br /&gt;
	Thoses apps are the basics apps that every children need to have.&lt;br /&gt;
&lt;br /&gt;
This rewriting is needed to merge apps from Sugar/Fedora and Sugarizer/Web.&lt;br /&gt;
Those apps tends to be used by every childrens using either a XO or a Web Browser. (Including PhoneGap/Cordova supported platform such as Android/iOS).&lt;br /&gt;
&lt;br /&gt;
The goal of the project is to provide the same experience for childrens ignoring the devices they are on. Moving to PhoneGap/Cordova is a really great step for Sugar, it&#039;s a way to provide the Sugar experience to every child using the web standards.&lt;br /&gt;
&lt;br /&gt;
The main technologies to be used will be &#039;&#039;&#039;HTML5 and Javascript&#039;&#039;&#039;. The ability to read the Python source code is required in order to provide the same features for the Sugar Web apps as on the XO.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;I have identified many difficults parts : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
- The abstract of the the touch/click layer in order to handle childrens using a computer with a keyboard and a mouse but also a child using a touchscreen with a phone or a tablet.&lt;br /&gt;
&lt;br /&gt;
- Responsive design in order to get a usuable app on both small and big screens&lt;br /&gt;
&lt;br /&gt;
- The storage layer which as to save the app state but also videos and pictures resources.&lt;br /&gt;
&lt;br /&gt;
- Phone compatibility which can be tricky with inputs and drawings (iOS and Android are not always acting the same way and need code customisations)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Libraries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
These are some libraries that I will look into in order to accelerate the development. The libraries are all at least MIT licensed. This is not a definitive choice, iOS and Android compatibility has to be checked.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EaselJS&#039;&#039;&#039; is a library made for working with canvas. I will definitely use it for the games development.  It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;wPaint&#039;&#039;&#039; is a jQuery plugin used to create &amp;quot;Paint like&amp;quot; apps. It has a builtin support of undo/redo. I think it&#039;s a great start for the Paint App. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RecordRTC&#039;&#039;&#039; is a Javascript-based media-recording library. I will look into this library to develop the Record app. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;JSXGraph&#039;&#039;&#039; is a Javascript library used for geometry and function plotting. I will use it for the Calc app. It is LGPL/MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Math.js&#039;&#039;&#039; is a Javascript library used for expression parsing. It will be used for the Calc app. It is Apache licensed.&lt;br /&gt;
&lt;br /&gt;
I will develop step by step using an Agile methodology.&lt;br /&gt;
&lt;br /&gt;
I have downloaded the Calculate, Paint, Memorize and Record xo files and will mimic their GUI.&lt;br /&gt;
My apps will have the same look and feel that the natives ones.&lt;br /&gt;
&lt;br /&gt;
My timeline&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Week 0 || Research Work on frameworks compatibility (phone, tablets and XO laptop located at Le Spot Bouygues)&lt;br /&gt;
|-&lt;br /&gt;
| Week 1 - 19 May || Calculate application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Base mathematical expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Results displaying and saving inside the Journal&lt;br /&gt;
|-&lt;br /&gt;
| Week 2 - 25 May || Calculate application :&lt;br /&gt;
Advanced mathematicals expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Graph support&amp;lt;br&amp;gt;&lt;br /&gt;
Ouput format controls (digits, bases)&amp;lt;br&amp;gt;&lt;br /&gt;
Input buttons for sin,cos, etc&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 3 - 1 June || Calculate application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Paint application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Basic drawing&amp;lt;br&amp;gt;&lt;br /&gt;
Color palette&amp;lt;br&amp;gt;&lt;br /&gt;
Undo / Redo&amp;lt;br&amp;gt;&lt;br /&gt;
Text typing support&amp;lt;br&amp;gt;&lt;br /&gt;
Saving to the Journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 4 - 8 June || Paint application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Memorize application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Base game context&amp;lt;br&amp;gt;&lt;br /&gt;
Grid size picker&amp;lt;br&amp;gt;&lt;br /&gt;
Default grid creation&amp;lt;br&amp;gt;&lt;br /&gt;
Ability to play the Game&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 5 - 15 June || Memorize application programming :&lt;br /&gt;
Grid creation using images, text and sound from Journal&amp;lt;br&amp;gt;&lt;br /&gt;
Grid saving to the Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Load game from journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 6 - 22 June || Memorize application programming :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Record application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Picture taking&amp;lt;br&amp;gt;&lt;br /&gt;
Publishing pictures to Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MidTerm Evaluation | MidTerm Evaluation&lt;br /&gt;
|-&lt;br /&gt;
| Week 7 - 29 June || Planning scheduling evaluation and modifications if required&lt;br /&gt;
All apps checking&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 8 - 6 July || Record application programming :&lt;br /&gt;
Sound recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Sound publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Week 9 - 13 July || Record application programming :&lt;br /&gt;
Video recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Video publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 10 - 20 July || Calc and Paint app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 11 - 27 July || Memorize and Record app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 12 - 3 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 13 -  10 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 14 - 17 August || Final patches in order to make everything working flawlessly&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#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;
I am really dedicated to my work, I can&#039;t stand doing something and not finishing it.&lt;br /&gt;
&lt;br /&gt;
I like when working really hard gets to something : my scolarity is great, my GPA is 4 (out of 4).&lt;br /&gt;
I&#039;ve led a R&amp;amp;D laboratory in my school focused on Google Technologies (Android / Dart / Angular / Go).&lt;br /&gt;
Our goal was to  keep track on the student&#039;s free projects and give them advices and workshops to discover new technologies.&lt;br /&gt;
&lt;br /&gt;
I got seen by my school and proposed to work with the GIGN on a serious project, I can&#039;t say any details but this was a great opportunity.&lt;br /&gt;
After this project, I got hired as I&#039;m now a &amp;quot;Innovation Mentor&amp;quot; for my school and keep track on students inside the national innovation lab (12 cities).&lt;br /&gt;
&lt;br /&gt;
This year I worked with big companies from Bouygues, thanks to Lionel Laské, on making innovation prototypes using new technologies such as the Google Glass or iBeacons.&lt;br /&gt;
&lt;br /&gt;
I really like to learn by myself and to discover new horizons and that&#039;s why I&#039;m writing this today. &lt;br /&gt;
My two formers internships were about Mobile and PhoneGap/Cordova using HTML5/JS. I think I can handle the amount of work of this project and contribute to the community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==You and the community==&lt;br /&gt;
&#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;
&#039;&#039;&#039;My answer : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I think this will be a great move for Sugar onto web platforms.&lt;br /&gt;
Sugarizer will allow everyone with every device to access the same user experience with the same look and feel.&lt;br /&gt;
This is really important to provide a standard way to use Sugar, essentially when kids are involved in the using. Using web standards will allow a new way for developpers to developp and for users to discovers the possibilities provided by Sugar.&lt;br /&gt;
Thoses apps are the basics apps required to make Sugarizer a really great thing to use.&lt;br /&gt;
I hope Sugarizer will allow every child, ignoring their devices to acces education through Sugarizer !&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lionel Laské :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugarizer is a way to look forward on Sugar future. But to start a real deployment with Sugarizer, we need to include inside the activities most used today by children and teachers on Sugar. More, this basic set of activities is an important source of content for other activities in Sugar ecosystem: Record activity for example will be the main source of content for Memory, Fototoon, Write or Paint activity. So this project is really a bootstrap for the development of Sugar Web.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Martin Abente Lahaye :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It&#039;s been a while since we started with JavaScript activities and I think its time that we cover such basic set of activities. Record is especially interesting as I haven&#039;t seen anything similar for the web. This would help projects such as Sugarizer to offer a more complete experience of Sugar in the web.&lt;br /&gt;
&lt;br /&gt;
&#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;
I will ask the Sugar community, friends, collegues and my school mentors to discuss with me in order to explain what my problem is.&lt;br /&gt;
&lt;br /&gt;
I think that discussion is the first step of getting new opinions and others point of view.&lt;br /&gt;
Of course I will also use my great friends, Google, StackOverflow, Github to see if somebody has encountered the same problems I did.&lt;br /&gt;
&lt;br /&gt;
&#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 think that I will setup a blog, in order to show what the project progress is. This blog will be updated with technical and non technical posts in order to allow everyone to understand what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
- I will (if it is relevant) create pages on the Sugar wiki&lt;br /&gt;
&lt;br /&gt;
- The Git commit messages will be clear and helpfull for others developpers&lt;br /&gt;
&lt;br /&gt;
- My code will be documented in order to reveal my work and progression&lt;br /&gt;
&lt;br /&gt;
- I will also use IRC to discuss with over people in order to get their opinions of the progress and or any problem I could have.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Miscellaneous==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Screenshot of the Sugar development environment&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;sugar-home-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I like to discover things, one of the best experience I had was around 2000, close to the summer when I discovered that it was possible do create things on a computer&lt;br /&gt;
&lt;br /&gt;
I remember going in the computer room and to discover Macromedia Flash. In this session we were in pairs and I really enjoyed using the software to draw stickmens.&lt;br /&gt;
&lt;br /&gt;
This really looks simple to me now that I&#039;m a programmer running on ArchLinux every day.&lt;br /&gt;
I think that we had only made 5 or 6 frames but it was animated and I found it awesome :)&lt;br /&gt;
&lt;br /&gt;
Simple things can change our perceptions and made people want to do things, I&#039;m sure that my choice of studies is really close to the education and friends I had.&lt;br /&gt;
&lt;br /&gt;
&#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;
Eveything is okay !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;Xo-and-i-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:2015 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=103146</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=103146"/>
		<updated>2019-07-09T08:32:56Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Replaced content with &amp;quot;Outdated, should be removed&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Outdated, should be removed&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018/Sugarizer_School_box&amp;diff=101767</id>
		<title>Summer of Code/2018/Sugarizer School box</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018/Sugarizer_School_box&amp;diff=101767"/>
		<updated>2018-05-04T16:03:49Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: May, 4th meeting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Meetings ===&lt;br /&gt;
&lt;br /&gt;
==== Sugarizer School Box Meeting - May, 4th 2018 ====&lt;br /&gt;
&lt;br /&gt;
===== Attendees =====&lt;br /&gt;
- Michaël Ohayon&lt;br /&gt;
&lt;br /&gt;
- Aman Sharma&lt;br /&gt;
&lt;br /&gt;
- Hrishi Patel&lt;br /&gt;
&lt;br /&gt;
===== Meeting topics =====&lt;br /&gt;
- Work Progress&lt;br /&gt;
&lt;br /&gt;
- Github repository refactoring&lt;br /&gt;
&lt;br /&gt;
- CI / CD&lt;br /&gt;
&lt;br /&gt;
===== Short summary =====&lt;br /&gt;
- Aman was working on the adding of Docker into the image&lt;br /&gt;
&lt;br /&gt;
- Refactoring of the repository should be done to better understand what is the need and use of the project : https://github.com/amanharitsh123/sugarizer-school-box/issues/2&lt;br /&gt;
&lt;br /&gt;
- We need to find a way to add continuous integration to the image building&lt;br /&gt;
&lt;br /&gt;
- We need to find a way to avoid requiring internet on first boot for docker installation&lt;br /&gt;
&lt;br /&gt;
==== Sugarizer School Box Meeting - April, 27th 2018 ====&lt;br /&gt;
&lt;br /&gt;
===== Attendees =====&lt;br /&gt;
- Michaël Ohayon&lt;br /&gt;
&lt;br /&gt;
- Aman Sharma&lt;br /&gt;
&lt;br /&gt;
- Rishabh Thaney&lt;br /&gt;
&lt;br /&gt;
- Hrishi Patel&lt;br /&gt;
&lt;br /&gt;
===== Meeting topics =====&lt;br /&gt;
- Congratulations Aman !&lt;br /&gt;
&lt;br /&gt;
- Community bonding period&lt;br /&gt;
&lt;br /&gt;
- Project Goals&lt;br /&gt;
&lt;br /&gt;
- Repository setup&lt;br /&gt;
&lt;br /&gt;
- Communication&lt;br /&gt;
&lt;br /&gt;
- Blog&lt;br /&gt;
&lt;br /&gt;
===== Short summary =====&lt;br /&gt;
- The bonding period will be a way to show Aman&#039;s former work on RPI and explain the project. It will allow him to continue working on the project and be fully ready to start when GSOC begins.&lt;br /&gt;
&lt;br /&gt;
- A new github repo will be created : sugarizer-school-box&lt;br /&gt;
&lt;br /&gt;
- The background and needs of the project has been told&lt;br /&gt;
&lt;br /&gt;
- The first priority is the pi project with sugarizer server (using the docker way of installation)&lt;br /&gt;
&lt;br /&gt;
- We all agreed on &amp;quot;The more automation, the better&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- Cron to trigger updates of the docker sugarizer server&lt;br /&gt;
&lt;br /&gt;
- We agreed to keep in mind that at some point, we will put the image generation in Continuous Integration platforms. Once again, we will do as many automation as possible.&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018/Sugarizer_School_box&amp;diff=101733</id>
		<title>Summer of Code/2018/Sugarizer School box</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018/Sugarizer_School_box&amp;diff=101733"/>
		<updated>2018-04-27T16:43:04Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Created Meetings section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Meetings ===&lt;br /&gt;
&lt;br /&gt;
==== Sugarizer School Box Meeting - April, 27th 2018 ====&lt;br /&gt;
&lt;br /&gt;
===== Attendees =====&lt;br /&gt;
- Michaël Ohayon&lt;br /&gt;
&lt;br /&gt;
- Aman Sharma&lt;br /&gt;
&lt;br /&gt;
- Rishabh Thaney&lt;br /&gt;
&lt;br /&gt;
- Hrishi Patel&lt;br /&gt;
&lt;br /&gt;
===== Meeting topics =====&lt;br /&gt;
- Congratulations Aman !&lt;br /&gt;
&lt;br /&gt;
- Community bonding period&lt;br /&gt;
&lt;br /&gt;
- Project Goals&lt;br /&gt;
&lt;br /&gt;
- Repository setup&lt;br /&gt;
&lt;br /&gt;
- Communication&lt;br /&gt;
&lt;br /&gt;
- Blog&lt;br /&gt;
&lt;br /&gt;
===== Short summary =====&lt;br /&gt;
- The bonding period will be a way to show Aman&#039;s former work on RPI and explain the project. It will allow him to continue working on the project and be fully ready to start when GSOC begins.&lt;br /&gt;
&lt;br /&gt;
- A new github repo will be created : sugarizer-school-box&lt;br /&gt;
&lt;br /&gt;
- The background and needs of the project has been told&lt;br /&gt;
&lt;br /&gt;
- The first priority is the pi project with sugarizer server (using the docker way of installation)&lt;br /&gt;
&lt;br /&gt;
- We all agreed on &amp;quot;The more automation, the better&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- Cron to trigger updates of the docker sugarizer server&lt;br /&gt;
&lt;br /&gt;
- We agreed to keep in mind that at some point, we will put the image generation in Continuous Integration platforms. Once again, we will do as many automation as possible.&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018&amp;diff=101263</id>
		<title>Summer of Code/2018</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018&amp;diff=101263"/>
		<updated>2018-01-25T14:15:12Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Project Ideas */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Sponsored Projects ==&lt;br /&gt;
&lt;br /&gt;
[https://summerofcode.withgoogle.com/organizations/5544862897143808/ Sugar Labs at GSoC]&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
|-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!Title&lt;br /&gt;
!Mentor&lt;br /&gt;
!Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Internationalization and Localization&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; |Chris Leonard&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details.  See [[Translation Team]] for framework description.&lt;br /&gt;
;Expected results: Work flow improvements for i18n&lt;br /&gt;
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Full-color icons&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; |Design team&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we&#039;d lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.)&lt;br /&gt;
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing&lt;br /&gt;
;Knowledge prerequisites: Knowledge of GTK; Python.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks optimizations&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.&lt;br /&gt;
;Expected results: A more robust and responsive Music Blocks.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of JavaScript, unit testing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Going Beyond Equal Temperament in Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics.  See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]&lt;br /&gt;
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of JavaScript, music theory&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Maintenance of activities.sugarlabs.org (ASLO)&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Sam CG&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded.  During GSoC 2017 we built ASLO v3 to address a number of deficiencies. But we have a few odds and ends that need to be addressed to bring the new site on line.&lt;br /&gt;
;Expected results: Update missing license and repository info on the activities found in the Sugar Labs github repository. Popular the database for the new ASLO. Do extensive testing (including creating some test suites.) Document future maintenance on the Wiki.&lt;br /&gt;
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git.  See [https://github.com/sugarlabs/aslo-v3].  &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Lesson Plans for Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
Hrishi Patel&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need some more scaffolding in the form of lesson plans.&lt;br /&gt;
;Expected results: A website and PDF document that can be bound.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of music theory, writing skills&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Just say no to GTK2&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Ignacio Rodriguez&amp;lt;br&amp;gt;Cristian Garcia&lt;br /&gt;
Abhijit Patel&amp;lt;br&amp;gt;Ibiam Chihurumnaya&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.&lt;br /&gt;
;Expected results: New versions of at least 25 existing Sugar activities.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of GTK, GST, and Python&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Updating a new design of Sugarlabs wiki&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: we are lacking in look of wiki.sugarlabs.org page. It looks ugly and unfriendly and need to be updated with a good design&lt;br /&gt;
;Expected results: New design of Wiki page of Sugarlabs&lt;br /&gt;
;Knowledge prerequisites: Knowledge of mediawiki and use of some basic languages&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Outreach&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We don&#039;t have a very friendly approach to outreach to new contributors. It would be great to make it easier to get involved and to navigate the path towards contributing to Sugar Labs. The goal of this project is to revamp our approach to outreach. &lt;br /&gt;
;Expected results: A set of pages similar to [https://publiclab.github.io/community-toolbox/] and [https://publiclab.org/wiki/software-outreach]&lt;br /&gt;
;Knowledge prerequisites: community outreach experience; some coding experience (to create requisite artifacts)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making a Beginner Guide&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We don&#039;t have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these &amp;quot;form where to start? , What to start? , How to start? , Where to submit? &amp;quot; . [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Example] The goal of this project is to Help newcomers to get introduce in easy way to the world of Sugar Labs&lt;br /&gt;
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily&lt;br /&gt;
;Knowledge prerequisites: community research , GitHub , coding experience ( HTML, CSS )&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |New Social Sugarlabs website&amp;lt;br&amp;gt;[[File:Social Site.jpg|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Its a social website that can be used to attract maximum users and everything ( Blogs, New projects, Softwares, Activities, etc) can be uploaded on it which will attract more user and create their interest &lt;br /&gt;
;Expected results: It should be over viewed by people around the world&lt;br /&gt;
;Knowledge prerequisites: Good Layout designing and coding experience&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making a marketing animated website page of sugarlabs&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:We need to develop a link that is website-page that will include a page with animations explaining all the things we have in Sugarlabs (as a marketing) like these examples [http://meta-liquid.com/  See[1] ], [http://education.iceandsky.com/ See [2] ]&lt;br /&gt;
;Expected results: A UI/UX layout and a main page that can be used to market the things in an animated way &lt;br /&gt;
;Knowledge prerequisites: Knowledge of marketing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP, Ruby)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. &amp;quot;what works&amp;quot; and &amp;quot;what needs to be done&amp;quot;. [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.&lt;br /&gt;
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.&lt;br /&gt;
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Migrating Planet Sugar to Medium&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:We need to change the look of [http://planet.sugarlabs.org/ Planet Sugar] by embedding [https://medium.com/ Medium] ( a blogger )into it by using Medium API but design should be changed&amp;gt; Better and interactive layout  &lt;br /&gt;
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making Testimonials page on Sugar Labs website&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:Well, Develop a testimonal webpage on Sugarlabs website by making a good research about the users who have experienced the world of Sugar. That should include videos, blog posts and many more things. For such type of layout example visit ( https://www.chownow.com/testimonials-reviews ) and ( https://www.codecademy.com/stories )&lt;br /&gt;
;Expected results: A good layout with more views about sugar Users&lt;br /&gt;
;Knowledge prerequisites: Make a research about people using Sugar ...get interaction with them ; know about Sugarlabs  and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks&#039; First Steps for Robotics &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps&lt;br /&gt;
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)&lt;br /&gt;
;Knowledge prerequisites: Understanding of Javascript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstratable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Create Examples, Compositions, and New Experiments Every Day! &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.&lt;br /&gt;
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC&lt;br /&gt;
;Knowledge prerequisites: Understanding of Music Blocks program; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (timeframes, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definate plus.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks UI Improvements and Implementation &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.&lt;br /&gt;
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand &amp;quot;what Music Blocks style is&amp;quot; (obviously this may change in the future, but a thoughtful rationale for the new style is expected).&lt;br /&gt;
;Knowledge prerequisites: Understanding of CSS, Javascript, and HTML. Published work on UI (links to code, websites, etc)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Scales/Modes/Keys Design Improvements and Implementation &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Marnen Laibow-Koser&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?&lt;br /&gt;
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.&lt;br /&gt;
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that a future (or current) developer could read and implement.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Create UI features for music analysis and visualization &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima &lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style&#039;s particular rules.&lt;br /&gt;
;Expected results: New Features.&lt;br /&gt;
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; javascript knowledge&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks Musical Ornaments Features &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.&lt;br /&gt;
;Expected results: New Features, documentation, and new example programs for each new feature.&lt;br /&gt;
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks Widget Improvements &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]&lt;br /&gt;
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.&lt;br /&gt;
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)&lt;br /&gt;
|-&lt;br /&gt;
|Making Sugarizer easy to package and deploy&lt;br /&gt;
|Michaël Ohayon&lt;br /&gt;
&lt;br /&gt;
Lionel Laské&lt;br /&gt;
|&lt;br /&gt;
;Brief explanation&lt;br /&gt;
:[https://github.com/llaske/sugarizer-server Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.&lt;br /&gt;
:Two evolutions could simplify the deployment process to make Sugarizer attractive for schools.&lt;br /&gt;
:1 - Package an image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network.&lt;br /&gt;
:2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku.&lt;br /&gt;
:&lt;br /&gt;
;Expected results:Raspberry Pi image files. Deployment scripts.&lt;br /&gt;
;Knowledge prerequisites:Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018&amp;diff=101262</id>
		<title>Summer of Code/2018</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2018&amp;diff=101262"/>
		<updated>2018-01-25T13:15:01Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Added Sugarizer package / deploy project&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Sponsored Projects ==&lt;br /&gt;
&lt;br /&gt;
[https://summerofcode.withgoogle.com/organizations/5544862897143808/ Sugar Labs at GSoC]&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
|-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!Title&lt;br /&gt;
!Mentor&lt;br /&gt;
!Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Internationalization and Localization&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; |Chris Leonard&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details.  See [[Translation Team]] for framework description.&lt;br /&gt;
;Expected results: Work flow improvements for i18n&lt;br /&gt;
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Full-color icons&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; |Design team&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we&#039;d lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.)&lt;br /&gt;
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing&lt;br /&gt;
;Knowledge prerequisites: Knowledge of GTK; Python.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks optimizations&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.&lt;br /&gt;
;Expected results: A more robust and responsive Music Blocks.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of JavaScript, unit testing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Going Beyond Equal Temperament in Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics.  See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]&lt;br /&gt;
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of JavaScript, music theory&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Maintenance of activities.sugarlabs.org (ASLO)&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Sam CG&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded.  During GSoC 2017 we built ASLO v3 to address a number of deficiencies. But we have a few odds and ends that need to be addressed to bring the new site on line.&lt;br /&gt;
;Expected results: Update missing license and repository info on the activities found in the Sugar Labs github repository. Popular the database for the new ASLO. Do extensive testing (including creating some test suites.) Document future maintenance on the Wiki.&lt;br /&gt;
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git.  See [https://github.com/sugarlabs/aslo-v3].  &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Lesson Plans for Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
Hrishi Patel&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need some more scaffolding in the form of lesson plans.&lt;br /&gt;
;Expected results: A website and PDF document that can be bound.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of music theory, writing skills&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Just say no to GTK2&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Ignacio Rodriguez&amp;lt;br&amp;gt;Cristian Garcia&lt;br /&gt;
Abhijit Patel&amp;lt;br&amp;gt;Ibiam Chihurumnaya&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.&lt;br /&gt;
;Expected results: New versions of at least 25 existing Sugar activities.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of GTK, GST, and Python&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Updating a new design of Sugarlabs wiki&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: we are lacking in look of wiki.sugarlabs.org page. It looks ugly and unfriendly and need to be updated with a good design&lt;br /&gt;
;Expected results: New design of Wiki page of Sugarlabs&lt;br /&gt;
;Knowledge prerequisites: Knowledge of mediawiki and use of some basic languages&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Outreach&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We don&#039;t have a very friendly approach to outreach to new contributors. It would be great to make it easier to get involved and to navigate the path towards contributing to Sugar Labs. The goal of this project is to revamp our approach to outreach. &lt;br /&gt;
;Expected results: A set of pages similar to [https://publiclab.github.io/community-toolbox/] and [https://publiclab.org/wiki/software-outreach]&lt;br /&gt;
;Knowledge prerequisites: community outreach experience; some coding experience (to create requisite artifacts)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making a Beginner Guide&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We don&#039;t have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these &amp;quot;form where to start? , What to start? , How to start? , Where to submit? &amp;quot; . [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Example] The goal of this project is to Help newcomers to get introduce in easy way to the world of Sugar Labs&lt;br /&gt;
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily&lt;br /&gt;
;Knowledge prerequisites: community research , GitHub , coding experience ( HTML, CSS )&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |New Social Sugarlabs website&amp;lt;br&amp;gt;[[File:Social Site.jpg|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Its a social website that can be used to attract maximum users and everything ( Blogs, New projects, Softwares, Activities, etc) can be uploaded on it which will attract more user and create their interest &lt;br /&gt;
;Expected results: It should be over viewed by people around the world&lt;br /&gt;
;Knowledge prerequisites: Good Layout designing and coding experience&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making a marketing animated website page of sugarlabs&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:We need to develop a link that is website-page that will include a page with animations explaining all the things we have in Sugarlabs (as a marketing) like these examples [http://meta-liquid.com/  See[1] ], [http://education.iceandsky.com/ See [2] ]&lt;br /&gt;
;Expected results: A UI/UX layout and a main page that can be used to market the things in an animated way &lt;br /&gt;
;Knowledge prerequisites: Knowledge of marketing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP, Ruby)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. &amp;quot;what works&amp;quot; and &amp;quot;what needs to be done&amp;quot;. [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.&lt;br /&gt;
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.&lt;br /&gt;
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Migrating Planet Sugar to Medium&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Samson Goddy&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:We need to change the look of [http://planet.sugarlabs.org/ Planet Sugar] by embedding [https://medium.com/ Medium] ( a blogger )into it by using Medium API but design should be changed&amp;gt; Better and interactive layout  &lt;br /&gt;
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Making Testimonials page on Sugar Labs website&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Jaskirat Singh&amp;lt;br&amp;gt;Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation:Well, Develop a testimonal webpage on Sugarlabs website by making a good research about the users who have experienced the world of Sugar. That should include videos, blog posts and many more things. For such type of layout example visit ( https://www.chownow.com/testimonials-reviews ) and ( https://www.codecademy.com/stories )&lt;br /&gt;
;Expected results: A good layout with more views about sugar Users&lt;br /&gt;
;Knowledge prerequisites: Make a research about people using Sugar ...get interaction with them ; know about Sugarlabs  and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks&#039; First Steps for Robotics &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps&lt;br /&gt;
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)&lt;br /&gt;
;Knowledge prerequisites: Understanding of Javascript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstratable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Create Examples, Compositions, and New Experiments Every Day! &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.&lt;br /&gt;
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC&lt;br /&gt;
;Knowledge prerequisites: Understanding of Music Blocks program; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (timeframes, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definate plus.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks UI Improvements and Implementation &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.&lt;br /&gt;
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand &amp;quot;what Music Blocks style is&amp;quot; (obviously this may change in the future, but a thoughtful rationale for the new style is expected).&lt;br /&gt;
;Knowledge prerequisites: Understanding of CSS, Javascript, and HTML. Published work on UI (links to code, websites, etc)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Scales/Modes/Keys Design Improvements and Implementation &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Marnen Laibow-Koser&amp;lt;br&amp;gt;Sachiko Nakajima&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?&lt;br /&gt;
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.&lt;br /&gt;
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that a future (or current) developer could read and implement.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Create UI features for music analysis and visualization &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima &lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style&#039;s particular rules.&lt;br /&gt;
;Expected results: New Features.&lt;br /&gt;
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; javascript knowledge&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks Musical Ornaments Features &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.&lt;br /&gt;
;Expected results: New Features, documentation, and new example programs for each new feature.&lt;br /&gt;
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks Widget Improvements &amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&amp;lt;br&amp;gt;Sachiko Nakajima&amp;lt;br&amp;gt;Marnen Laibow-Koser&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]&lt;br /&gt;
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.&lt;br /&gt;
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)&lt;br /&gt;
|-&lt;br /&gt;
|Making Sugarizer easy to package and deploy&lt;br /&gt;
|Michaël Ohayon&lt;br /&gt;
&lt;br /&gt;
Lionel Laské&lt;br /&gt;
|&lt;br /&gt;
;Brief explanation&lt;br /&gt;
:[https://github.com/llaske/sugarizer-server Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.&lt;br /&gt;
:Two evolutions could simplify the deployment process to make Sugarizer attractive for schools.&lt;br /&gt;
:1 - Package an image for Raspberry Pi that could be flashed on a sd card and that could bring sugarizer client and/or server (customizable)&lt;br /&gt;
:2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku.&lt;br /&gt;
:&lt;br /&gt;
;Expected results:Raspberry Pi image files. Deployment scripts.&lt;br /&gt;
;Knowledge prerequisites:Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2017&amp;diff=99947</id>
		<title>Summer of Code/2017</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2017&amp;diff=99947"/>
		<updated>2017-02-13T21:09:34Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Adding Sugarizer Deployement and Management Tool for Android idea&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
|-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!Title&lt;br /&gt;
!Mentor&lt;br /&gt;
!Project&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Internationalization and Localization&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; |Chris Leonard&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details.&lt;br /&gt;
;Expected results: Work flow improvements for i18n&lt;br /&gt;
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |New Back-end Server for Turtle Blocks and Music Blocks&amp;lt;br&amp;gt;[[File:Git logo.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Vikram Ahuja&amp;lt;br&amp;gt;Ignacio Rodriguez&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.&lt;br /&gt;
;Expected results: Deployment of &amp;quot;git&amp;quot; back end.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Going Beyond Equal Temperament in Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics.&lt;br /&gt;
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of JavaScript, music theory&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Giving Sugar Labs Website a New Look&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Ignacio Rodriguez&amp;lt;br&amp;gt;Samson Goddy&amp;lt;br&amp;gt;Dave Crossland&amp;lt;br&amp;gt;Tymon Radzik&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).&lt;br /&gt;
;Expected results: Deployment of a new website for Sugar Labs&lt;br /&gt;
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Maintenance of activities.sugarlabs.org (ASLO)&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | (volunteers?)&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded.  Some maintenance tasks are needed.  Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.&lt;br /&gt;
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered.  Fix downloads by new versions of Sugar; old versions are offered.  Make activity maintainer take-over easier; not easy at the moment.  Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old.  Show new activity.info metadata such as source repository.  Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&amp;amp;status=assigned&amp;amp;status=new&amp;amp;status=reopened&amp;amp;component=activities.sugarlabs.org&amp;amp;col=id&amp;amp;col=summary&amp;amp;col=priority&amp;amp;col=status&amp;amp;col=owner&amp;amp;col=type&amp;amp;col=milestone&amp;amp;order=priority activities.sugarlabs.org].  Semi-automate common maintenance tasks; like adding a new Sugar version.  Document future maintenance on the Wiki.&lt;br /&gt;
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git.  See [https://github.com/sugarlabs/aslo source code].  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |School Management Backend&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn&#039;t have any mechanism for managing courses/curriculum/administrative functions commonly found in &amp;quot;school management systems&amp;quot;. It could be possible to overlay on top of Sugar web-services such a toolkit.&lt;br /&gt;
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.&lt;br /&gt;
;Knowledge prerequisites: Python, django&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Timbre Widget for Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.&lt;br /&gt;
;Expected results: a working widget for Music Blocks for manipulating Timbre.&lt;br /&gt;
;Knowledge prerequisites: JavaScript&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Sugarizer Server Dashboard&amp;lt;br&amp;gt;[[File:Dashboard server.png|90px|thumb|center]] &lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Lionel Laské&amp;lt;br&amp;gt;Michaël Ohayon&lt;br /&gt;
|align=left valign=top |&lt;br /&gt;
&lt;br /&gt;
;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the &amp;quot;Sugarizer Server Dashboard&amp;quot;. This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.&lt;br /&gt;
&lt;br /&gt;
;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:&lt;br /&gt;
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.&lt;br /&gt;
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.&lt;br /&gt;
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.&lt;br /&gt;
* Graphic and request: display graphics and report on previous data.&lt;br /&gt;
&lt;br /&gt;
;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB&lt;br /&gt;
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Sugarizer Deployement and Management Tool for Android&amp;lt;br&amp;gt;&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Michaël Ohayon&amp;lt;br&amp;gt;Lionel Laské&lt;br /&gt;
|align=left valign=top |&lt;br /&gt;
&lt;br /&gt;
;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the &amp;quot;Sugarizer Deployment and Management Tool for Android&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).&lt;br /&gt;
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.&lt;br /&gt;
* Application Manager : Install or remove applications using APK files.&lt;br /&gt;
* File Manager : Add / Remove files&lt;br /&gt;
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.&lt;br /&gt;
* Scenario Writer : Allow &#039;&#039;&#039;non developpers&#039;&#039;&#039;  to create sequences to perform all the steps previously defined.&lt;br /&gt;
&lt;br /&gt;
;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX &lt;br /&gt;
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |User Manual for Music Blocks&amp;lt;br&amp;gt;[[File:Music-Blocks.png|90px|thumb|center]]&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Walter Bender&amp;lt;br&amp;gt;Devin Ulibarri&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.&lt;br /&gt;
;Expected results: A website and PDF document that can be bound.&lt;br /&gt;
;Knowledge prerequisites: Knowledge of music theory, writing skills&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Just say no to GTK2&lt;br /&gt;
| valign=top width=&amp;quot;15%&amp;quot; | Ignacio Rodriguez&amp;lt;br&amp;gt;Sam Parkinson&lt;br /&gt;
| align=left valign=top |&lt;br /&gt;
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.&lt;br /&gt;
;Expected results: New versions of Turtle, Speak, Chat, Record, and a dozen others&lt;br /&gt;
;Knowledge prerequisites: Knowledge of GTK, GST, and Python&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2016&amp;diff=97067</id>
		<title>Summer of Code/2016</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2016&amp;diff=97067"/>
		<updated>2016-03-05T20:58:10Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Sugarizer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Students&#039;&#039;&#039;: See our guide on [[Summer_of_Code#How_to_participate|how to participate in Google Summer of Code]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Project candidates ==&lt;br /&gt;
&lt;br /&gt;
In the table below is a list of projects potential participants might contribute to in the GSoC program.&lt;br /&gt;
&lt;br /&gt;
;Note 0: These are project ideas from Sugar Labs contributors. &#039;&#039;&#039;Students, feel free to propose your ideas as well.&#039;&#039;&#039;&lt;br /&gt;
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you&#039;d be willing to co-mentor.&lt;br /&gt;
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.&lt;br /&gt;
&lt;br /&gt;
== Sugar Core ==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Internationalization and Localization ||valign=top width=&amp;quot;15%&amp;quot; | Chris Leonard ||align=left valign=top|&lt;br /&gt;
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details.&lt;br /&gt;
;Expected results: Work flow improvements for i18n&lt;br /&gt;
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Journal Rethink ||valign=top width=&amp;quot;15%&amp;quot; | Sam Parkinson&amp;lt;br&amp;gt;Ignacio Rodríguez ||align=left valign=top|&lt;br /&gt;
;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating &amp;quot;projects&amp;quot; among other things.&lt;br /&gt;
;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[Image:Sugarlabs_mainpage_01.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Groups Rethink ||valign=top width=&amp;quot;15%&amp;quot; | Sam Parkinson&amp;lt;br&amp;gt;Ignacio Rodríguez ||align=left valign=top|&lt;br /&gt;
;Brief explanation: Sugar has a buddies/group zoom view, which is very limited.  It could be further integrated with sugar (eg. send to group, share with group, have a shared group journal) and expanded upon (having multiple groups user configured, like: a science prac group, a drama play group, etc.).&lt;br /&gt;
;Expected results: Working code for the Sugar and vague ideas (more concrete than this) defined ahead of time.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.  Knowledge of telepathy is might be helpful.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:reflect.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Reflect Activity||valign=top width=&amp;quot;15%&amp;quot; | Sam Parkinson and Walter Bender ||align=left valign=top|&lt;br /&gt;
;Brief explanation: The Sugar Journal is designed to be a place of reflection. We have the basic stub of a reflection activity that attempts to encourage more reflection and as a vehicle for sharing criticism. This idea needs more thought and coding.&lt;br /&gt;
;Expected results: A solid formulation of how the activity will work in the classroom and working code for the Reflect Activity.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:git_logo.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Git backend||valign=top width=&amp;quot;15%&amp;quot; | Martin Abente Lahaye and Walter Bender ||align=left valign=top|&lt;br /&gt;
;Brief explanation: The Sugar Journal doesn&#039;t do a great job of supporting versioning or forking. This project is to build a backend for the Journal that is based on git, which does support versioning and forking. By building on top of a git hosting site we get the added benefit of network access as well.&lt;br /&gt;
;Expected results: Working code and an integration with Turtle Blocks&lt;br /&gt;
;Knowledge prerequisite: Strong background in Git and scripting languages such as Python, Ruby and JavaScript.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | || valign=top  style=&amp;quot;background:#e3e4e5;&amp;quot;  | Performance tuning on machines with limited memory || valign=top | Samuel Greenfeld||align=left valign=top |&lt;br /&gt;
;Brief explanation: The newer Sugar builds have performance issues on some old hardware with limited memory. This is keeping some Sugar deployments from upgrading. This project is to look into the performance issues and tune Sugar for low-memory devices.&lt;br /&gt;
;Expected results: build suitable for running on OLPC XO-1 hardware&lt;br /&gt;
;Knowledge prerequisite:&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | || valign=top  style=&amp;quot;background:#e3e4e5;&amp;quot;  | Re-design collaboration with web technologies || valign=top | Martin Abente Lahaye and Walter Bender ||align=left valign=top |&lt;br /&gt;
;Brief explanation: Now that JavaScript has become a first class citizen in the Sugar ecosystem, we must re-design our collaboration model to allow collaboration between web activities regardless of the platform.&lt;br /&gt;
;Knowledge prerequisite: JavaScript, web sockets, web services.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sugar Activities ==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:confusion.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Beyond Flashcards: Programming to ReadJS||valign=top width=&amp;quot;15%&amp;quot; | Walter Bender||align=left valign=top|&lt;br /&gt;
;Brief explanation: Back in the 1980s, IBM had a literacy program, &amp;quot;Writing to Read&amp;quot;. The gist was that writing was a great way to spark a child&#039;s interest in reading. What if writing code could achieve a similar result? The project is to explore how programming might be incorporated into a literacy program. Like turtle, only simple sentences instead of stacks. It would be a &amp;quot;whole word&amp;quot; approach rather than a &amp;quot;phonics&amp;quot; approach: they can take &amp;quot;sentences&amp;quot; and make paragraphs that result in animations.&lt;br /&gt;
;Expected results: Working prototype&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python or JavaScript&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top |  ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Covert Record, Clock, Speak and Measure to gstreamer 1.0 ||valign=top width=&amp;quot;15%&amp;quot; | Ignacio Rodríguez ||align=left valign=top|&lt;br /&gt;
;Brief explanation: The vast majority of Activities that use gstreamer for sound have been converted to gstreamer 1.0 because the older 0.10 is now End of Life and is no longer being developed. It also adds quite a large set of extra duplicate dependencies to Sugar distributions. There&#039;s a lot of good examples of Activities that have been converted to provide excellent examples. The gstreamer 1.0 bindings are provided by gobject-introspection so it also assists in the conversion of Activities to gtk3.&lt;br /&gt;
;Expected results: As many of the above Activities converted to use gst 1.0&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python, gobject-introspection and gstreamer&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top |  ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Covert TamTam to Csound6 ||valign=top width=&amp;quot;15%&amp;quot; | &amp;lt;TBD&amp;gt; ||align=left valign=top|&lt;br /&gt;
;Brief explanation: TamTam makes extensive use of CSound, other Activities like Memorize, Pippy, and TurtleBlocks also can make use of CSound bindings. With the introduction of CSound 6 to a number of distributions TamTam needs migration to use the newer version of CSound.&lt;br /&gt;
;Expected results: Convert TamTam to use CSound6, possibly other Activities&lt;br /&gt;
;Knowledge prerequisite: Strong background in Python, background in CSound&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Music Widgets||valign=top width=&amp;quot;15%&amp;quot; | Devin Ulibarri ||align=left valign=top|&lt;br /&gt;
;Brief explanation: Development four new widgets to improve the possibilities for music&lt;br /&gt;
learning as well as overall user-experience for Music Blocks. The widgets are 1. Pitch-Staircase 2. Tempo 3. Rhythm Rulers, and 4. Free-Pitch Slider. Widgets will integrate with the current coding environment without disrupting the underlying language in any way (like the current pitch-time matrix).&lt;br /&gt;
;Expected results: Users will use these to explore musical concepts and generate desired&lt;br /&gt;
blocks from their experiments.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Javascript, Basic knowledge of Music Theory&lt;br /&gt;
and/or physics&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sugar Activities (and Ports) ==&lt;br /&gt;
&lt;br /&gt;
These are existing and new activities we&#039;d like to see enhanced. We expect that the activities will take on new UI features and pedagogical significance.&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Music Blocks Challenges||valign=top width=&amp;quot;15%&amp;quot; | Devin Ulibarri||align=left valign=top|&lt;br /&gt;
;Brief explanation: Development of the &amp;quot;Power Piece&amp;quot; concept for teaching music and programming. (Power Pieces introduce rich musical ideas that can be studied, analyzed, transformed, and re-imagined, they are ripe for open-ended explorations.)&lt;br /&gt;
;Expected results: A well-documented series of activities for exploring musical and programming concepts using the Music Blocks activity as a foundation.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Javascript, Music Theory&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Nutrition-icon.svg|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Nutritional Microworld||valign=top width=&amp;quot;15%&amp;quot; | w/Dr. Jessica Early||align=left valign=top|&lt;br /&gt;
;Brief explanation: We have the basic building blocks (Turtle Nutrition) for programming with food as a datatype. What we are missing is a collection of meaningful activities to use with the tool as exemplars. We want to develop a an open-ended, yet&lt;br /&gt;
relevant tool—one that invites learners to explore fundamental concepts of nutrition that are both intrinsic to nutrition yet transcendent of a specific discipline.&lt;br /&gt;
;Expected results: A well-documented series of activities for exploring nutrition that use the nutrition plugin as a basis. A series of workshops to study these ideas with children.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Javascript, some background in Nutrition.&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Turtle-Flags.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; |Turtle Confusion/Flags JS||valign=top width=&amp;quot;15%&amp;quot; | Walter Bender||align=left valign=top|&lt;br /&gt;
;Brief explanation: Port of Turtle Confusion and Turlte Flags.&lt;br /&gt;
;Expected results: A framework for creating challenges and a few exemplars.&lt;br /&gt;
;Knowledge prerequisite: Strong background in Javascript&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Tux Math||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
The TuxMath activity is popular with deployments. However, the upstream version appears to be abandoned. This task would be to implement a sugar-web-activity math game comparable to TuxMath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sugar Technology ==&lt;br /&gt;
&lt;br /&gt;
Sugar is based on the Python programming language and the GTK libraries. We also support some web technologies: HTML5, CSS, and JavaScript.&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Debugging.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Unit Testing ||valign=top width=&amp;quot;15%&amp;quot; | TBD ||align=left valign=top|&lt;br /&gt;
Deep dive into unit tests. We have a framework but it provides scant coverage for Sugar core and almost no coverage for Sugar activities.&lt;br /&gt;
;Brief Description: The goal is to develop tests for many more subsystems in Sugar core and to light a fire under the developer community to write tests for Sugar activities.&lt;br /&gt;
;Expected Results: a new test suite and scads of documentation.&lt;br /&gt;
;Knowledge Prerequisite: A strong background in Python.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sugar on the Ground ==&lt;br /&gt;
&lt;br /&gt;
A number of real-world issues crop up in deployments of Sugar, especially where resources are limited (bandwidth, CPU speed, battery life, local storage, etc.) These tasks are related to making Sugar more usable under such circumstances.&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal save option ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
&lt;br /&gt;
The Sugar Journal should provide a &#039;save/save as&#039; interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from &#039;current.activity&#039; to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document. &lt;br /&gt;
;Note: this approach satisfies the needs referenced in the git task. Git is a little like a hammer looking for a nail. Using git for this function will likely double the size of the data stored in the Journal (based on normal experience using git). Unfortunately, we don&#039;t have this space on the XOs. The standard save/save as gives the user the ability to manage versions by using unique names.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal as a service ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
&lt;br /&gt;
The Journal activity is currently implemented as an activity. It should be changed to a &#039;service&#039;. This means the Journal icon on the frame should be to the left of the zoom group icons to match the sequence on the keyboard. The Journal is always running as a service when the Sugar is running. It is accessible by the Journal key on the keyboard and also by the Journal button in the frame. When the view is switched to the Journal, clicking on the activity view (right most key of the zoom group) should switch the screen back to the current activity.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal backup and restore ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson&amp;lt;br&amp;gt;Ignacio Rodriguez||align=left valign=top|&lt;br /&gt;
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user&#039;s Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available). &lt;br /&gt;
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals&lt;br /&gt;
;Note: This would essentially accomplish the intent of the group/buddy task. Further, OwnCloud could be provided on a school server or on the internet. as appropriate.&lt;br /&gt;
;Note: There is a Sugar interface for saving to other cloud services, such as Google Docs, Dropbox, et al. that could be exploited.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal session data management ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
One goal of Sugar is to record information about user sessions. This is currently accomplished by creating statistics from the metadata stored in the Journal.&lt;br /&gt;
Unfortunately, a consequence is that the Journal view fills with essentially meaningless links to this metadata (mine fills with Terminal Activity and Log entries).&lt;br /&gt;
This makes it much harder for the user to identify meaningful Journal objects (documents, images, items from the library, ...). A mechanism is needed to that session data can be logged independently of the Journal view (i.e not shown on the screen). This logged information should be transferred to a backup repository (e.g. school server or USB drive) as soon as possible and deleted from the local store to free up space. The available reporting activities should be modified to use this new mechanism.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal quota management ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
The Journal icon provides information the amount of free space in the user&#039;s store. if this amount is less than 50MB, a dialog is shown requiring the user to switch to the Journal view and claiming that the &#039;Journal is Full&#039;. This message is, at best, misleading. The available storage can arise from several causes - the fact that an activities &#039;instance&#039; store was not deleted, the space required by installed activities, or space required by data files in /home/olpc/Library, or data stored by activities in &#039;data&#039;, &#039;instance&#039; or &#039;temp&#039;. Currently, Sugar provides no guidance or help to enable a user to deal with this problem short of reflashing the image. The goal of this task is to provide a quota management system on storage with a way for the user (e.g. by a special Sugar activity) to analyze the usage of storage and to save by usb key or school server or cloud storage large or currently unneeded items and then delete them. The system should show the user the size of items and provide updates on how much storage has been made free by his/her actions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Journal activity resume feature ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
In Sugar&#039;s Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.&lt;br /&gt;
&lt;br /&gt;
This task should set the Home View default to launch a new instance of the activity. The Alt key should be set to enable resuming a selected instance of the activity.  By serendipity, this also shows the Home View with black and white icons. Icons with color signifying a resumable instance use the colors associated with the laptop. Unfortunately many of these color combinations make the icon much more difficult to distinguish than the black and white version. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar Activity resume feature ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson&amp;lt;br&amp;gt;Ignacio Rodriguez ||align=left valign=top|&lt;br /&gt;
Sugar provides a &#039;web services&#039; capability. However, these services are only available to an XO which has connection to the internet. This is not useful to a large number of users who do not have internet access. The school server (e.g. XSCE) provides an alternative to the internet for many deployments. This task is to provide a capability on the school server to support some or all of the Sugar web services (e.g. by OwnCloud or ELGG). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar offline ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugar &amp;quot;on-boarding&amp;quot; ||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
Sugar users are often new to computers and not familiar with other operating systems. We need a mechanism to allow users to more quickly develop skills in using the capabilities of the XO (&#039;onboarding&#039;). One proposal is to develop scripts which lead the user through a series of interactive steps illustrating common usage of the XO with Sugar ([https://www.sam.today/blog/sugar-onboard-design.html]). This task is to implement an interpretive system that allows &lt;br /&gt;
deployments or experienced users to create an &#039;onboard&#039; script that guides the user to carry out a task. The referenced proposal suggests some user tasks where this mechanism could be employed. Since there is no finite list of these tasks, an interpretive approach enables the scripts to be created as necessary. &lt;br /&gt;
;For example: how does a user switch to the Gnome desktop? A script could be created guiding the user through the necessary steps. How does the user make a screen shot, use Gimp in the gnome desktop to crop and resize, and then insert it as an image in a Write document? How does the user initiate or join a chat?&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | 32bit Sugar on Ubuntu||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
Sugar is available on the XO and some other platforms. In particular, Sugar is available for 64-bit systems with Ubuntu 14.04 LTS installed (http://wiki.sugarlabs.org/go/Ubuntu). Unfortunately, this procedure does not work with 32-bit systems. There exists an opportunity to deploy Sugar &lt;br /&gt;
with relatively inexpensive or refurbished laptops which do not provide 64-bit support. This task is to create a comparable version of Sugar which can &lt;br /&gt;
be installed on 32-bit systems as an alternate Ubuntu desktop.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | One to Many Sugar||valign=top width=&amp;quot;15%&amp;quot; | Tony Anderson ||align=left valign=top|&lt;br /&gt;
The OLPC model is that each user has full possession and is the only user of an XO laptop. Therefore, Sugar assumes a 1-1 correspondence between users and XO serial numbers. However, Sugar is being used on other platforms (e.g. SOAS), where there is no obvious equivalent to a serial number. SOAS and James Cameron [citation?] have created versions of Sugar which do not assume the user is &#039;olpc&#039;, but implement a standard username/password login system. The users storage is allocated to his/her home directory. &lt;br /&gt;
&lt;br /&gt;
This task is to create a Sugar image for the XO which allows for user&#039;s to login by username and password. The basic task is to move the Activities folder to a common space so that only one copy is needed per system. This will support deployments where one set of laptops are shared across multiple classes (and users) or where there one laptop is shared between two students - one in a morning shift and the other in an afternoon shift. &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sugarizer ==&lt;br /&gt;
&lt;br /&gt;
[http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates a bunch of activities written for Sugar in Sugar Web.&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=3 style=&amp;quot;border: 1px solid white; border-collapse: collapse; background: #e3e4e5;&amp;quot;&lt;br /&gt;
 |-style=&amp;quot;background:#787878; color: white;&amp;quot;&lt;br /&gt;
!  !! Title !! Mentor !! Project&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugarizer OS ||valign=top width=&amp;quot;15%&amp;quot; | Lionel Laské and Michaël Ohayon||align=left valign=top|&lt;br /&gt;
The goal of this project is to create &amp;quot;Sugarizer OS&amp;quot;.&lt;br /&gt;
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.&lt;br /&gt;
&lt;br /&gt;
On Android, Sugarizer OS will take the form of an Android Launcher so it will be able to replace the standard Android launcher of the device. So the user will be able to launch both Sugarizer Activities and Android application from the Sugarizer home. The Sugarizer List View screen will let you choose which Android application icons will appear in the favorite view.&lt;br /&gt;
&lt;br /&gt;
Into Sugarizer OS the Neighborhood view will let the user see and connect to a WiFi hotspot as in Sugar. The Sugarizer OS settings will allow to access to Android settings and let the use to switch to the standard Android launcher.&lt;br /&gt;
&lt;br /&gt;
Prerequisite: Android, Java, HTML5/JavaScript.&lt;br /&gt;
&lt;br /&gt;
How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create your own APK following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#build-client-for-android-or-ios here]. Think about how to adapt this APK to transform it into an Android launcher.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Dashboard server.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugarizer Server Dashboard ||valign=top width=&amp;quot;15%&amp;quot; | Lionel Laské and Michaël Ohayon ||align=left valign=top|&lt;br /&gt;
The goal of this project is to create the &amp;quot;Sugarizer Server Dashboard&amp;quot;.&lt;br /&gt;
Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:&lt;br /&gt;
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.&lt;br /&gt;
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.&lt;br /&gt;
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.&lt;br /&gt;
* Graphic and request: display graphics and report on previous data.&lt;br /&gt;
&lt;br /&gt;
Technology to use: HTML5/JavaScript, bootstrap, node.js, MongoDB&lt;br /&gt;
&lt;br /&gt;
How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the  [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!valign=top | [[File:Fototoon-moon-speak.png|90px|thumb|center]] ||valign=top width=&amp;quot;15%&amp;quot; style=&amp;quot;background:#e3e4e5;&amp;quot; | Sugarizer Activity Set ||valign=top width=&amp;quot;15%&amp;quot; | Lionel Laské and Michaël Ohayon ||align=left valign=top|&lt;br /&gt;
The goal of this project is to port some famous Sugar activities into HTML5/JavaScript Sugar Web activities that will be include into the Sugarizer Package. Three activities will be ported:&lt;br /&gt;
* Moon: Moon is a Moon phase viewer, includes Lunar phase information and eclipse data.&lt;br /&gt;
* Speak: Speak is a talking face. Anything you type will be spoken aloud using the speech synthesizer, espeak.&lt;br /&gt;
* Fototoon: Fototoon is an activity that let user create cartoons using pictures from the journal.&lt;br /&gt;
&lt;br /&gt;
Technology to use: HTML5/JavaScript&lt;br /&gt;
&lt;br /&gt;
How to start: Download and install Sugar like explain [https://wiki.sugarlabs.org/go/Downloads here] and install the existing version of activities to port: [http://activities.sugarlabs.org/us/sugar/addon/4034 Moon], [http://activities.sugarlabs.org/us/sugar/addon/4038 Speak], [http://activities.sugarlabs.org/us/sugar/addon/4253 Fototoon]. Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create an empty Sugarizer activity following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#create-your-own-activity here]. Think about how to reproduce features of existing activities.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Subpages==&lt;br /&gt;
{{Special:PrefixIndex/{{PAGENAMEE}}/}}&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95821</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95821"/>
		<updated>2015-05-27T20:03:41Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Docker */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
This page presents how to run Sugar with Docker.&lt;br /&gt;
&lt;br /&gt;
You&#039;ll be able to run Sugar on your computer without having to install the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
Requirements : GNU/Linux, 64bits processor, Docker, Graphical Display&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
== Use cases ==&lt;br /&gt;
Docker is great for TESTING / DEVELOPING purposes&lt;br /&gt;
&lt;br /&gt;
It could be used to distribute Sugar but the XO specificities will strongly discourage this usage.&lt;br /&gt;
&lt;br /&gt;
== Pro / Cons ==&lt;br /&gt;
+ Docker will help you to easily try some activities if you haven&#039;t installed Sugar.&lt;br /&gt;
&lt;br /&gt;
+ It&#039;s fast and won&#039;t install anything on your computer&lt;br /&gt;
&lt;br /&gt;
- It needs to download the container image ~500mb&lt;br /&gt;
&lt;br /&gt;
- Won&#039;t allow to run every apps, and won&#039;t act exactly as the XO.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95820</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95820"/>
		<updated>2015-05-27T20:00:12Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Pro / Cons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
This page presents how to run Sugar with Docker.&lt;br /&gt;
&lt;br /&gt;
You&#039;ll be able to run Sugar on your computer without having to install the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
Requirements : GNU/Linux, 64bits processor, Docker, Graphical Display&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
== Pro / Cons ==&lt;br /&gt;
+ Docker will help you to easily try some activities if you haven&#039;t installed Sugar.&lt;br /&gt;
&lt;br /&gt;
+ It&#039;s fast and won&#039;t install anything on your computer&lt;br /&gt;
&lt;br /&gt;
- It needs to download the container image ~500mb&lt;br /&gt;
&lt;br /&gt;
- Won&#039;t allow to run every apps, and won&#039;t act exactly as the XO.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95819</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95819"/>
		<updated>2015-05-27T19:59:50Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Docker */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
This page presents how to run Sugar with Docker.&lt;br /&gt;
&lt;br /&gt;
You&#039;ll be able to run Sugar on your computer without having to install the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
Requirements : GNU/Linux, 64bits processor, Docker, Graphical Display&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
== Pro / Cons ==&lt;br /&gt;
+ Docker will help you to easily try some activities if you haven&#039;t installed Sugar.&lt;br /&gt;
+ It&#039;s fast and won&#039;t install anything on your computer&lt;br /&gt;
&lt;br /&gt;
- It needs to download the container image ~500mb&lt;br /&gt;
- Won&#039;t allow to run every apps, and won&#039;t act exactly as the XO.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95818</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95818"/>
		<updated>2015-05-27T19:55:28Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Docker */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
This page presents how to run Sugar with Docker.&lt;br /&gt;
&lt;br /&gt;
You&#039;ll be able to run Sugar on your computer without having to install the Sugar environment.&lt;br /&gt;
&lt;br /&gt;
Requirements : GNU/Linux, 64bits processor, Docker, Graphical Display&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95656</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95656"/>
		<updated>2015-05-15T15:38:45Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;This page is under construction&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Video=&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
    &lt;br /&gt;
  &amp;lt;video width=&amp;quot;400&amp;quot; controls&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.mp4&amp;quot; type=&amp;quot;video/mp4&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.ogg&amp;quot; type=&amp;quot;video/ogg&amp;quot;&amp;gt;&lt;br /&gt;
    Your browser does not support HTML5 video.&lt;br /&gt;
  &amp;lt;/video&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
==Record a video using the Webcam==&lt;br /&gt;
==Take a picture using the Webcam==&lt;br /&gt;
&lt;br /&gt;
=Audio=&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag&lt;br /&gt;
&lt;br /&gt;
  https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
  &lt;br /&gt;
  &amp;lt;audio controls&lt;br /&gt;
    src=&amp;quot;http://media.w3.org/2010/07/bunny/04-Death_Becomes_Fur.oga&amp;quot;&amp;gt;&lt;br /&gt;
    Your user agent does not support the HTML5 Audio element.&lt;br /&gt;
  &amp;lt;/audio&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  See http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  Volume is read-only on iOS.&lt;br /&gt;
  Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
== Record sound using the microphone ==&lt;br /&gt;
&lt;br /&gt;
=Input/Touch=&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95655</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95655"/>
		<updated>2015-05-15T14:39:05Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95654</id>
		<title>SugarOnDocker</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=SugarOnDocker&amp;diff=95654"/>
		<updated>2015-05-15T14:38:21Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Created page with &amp;quot;=Docker=  ==Introduction==  Docker allows to run programs using specific operating system onto every computer.   You can run a Sugar container using Fedora onto your computer...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Docker=&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Docker allows to run programs using specific operating system onto every computer.&lt;br /&gt;
  You can run a Sugar container using Fedora onto your computer without having to be on Fedora.&lt;br /&gt;
&lt;br /&gt;
The guest operating system is isolated from the host. When running Sugar onto Docker, you won&#039;t have to install Sugar dependencies or to be onto the same OS.&lt;br /&gt;
&lt;br /&gt;
==Run Sugar using Docker==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a script to easily run Sugar. It supports data persistance and .activity installation&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar&lt;br /&gt;
&lt;br /&gt;
===Usage===&lt;br /&gt;
&lt;br /&gt;
  git clone https://github.com/mikklfr/docker-sugar.git&lt;br /&gt;
  cd docker-sugar&lt;br /&gt;
  sh run.sh&lt;br /&gt;
&lt;br /&gt;
https://github.com/mikklfr/docker-sugar/raw/master/demo-small.gif&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Demo-sugar-docker.gif&amp;diff=95653</id>
		<title>File:Demo-sugar-docker.gif</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Demo-sugar-docker.gif&amp;diff=95653"/>
		<updated>2015-05-15T14:25:37Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: How to run Sugar onto Docker using https://github.com/mikklfr/docker-sugar&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How to run Sugar onto Docker using https://github.com/mikklfr/docker-sugar&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95652</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95652"/>
		<updated>2015-05-15T14:11:43Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;This page is under construction&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Video=&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
    &lt;br /&gt;
  &amp;lt;video width=&amp;quot;400&amp;quot; controls&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.mp4&amp;quot; type=&amp;quot;video/mp4&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.ogg&amp;quot; type=&amp;quot;video/ogg&amp;quot;&amp;gt;&lt;br /&gt;
    Your browser does not support HTML5 video.&lt;br /&gt;
  &amp;lt;/video&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
==Record a video using the Webcam==&lt;br /&gt;
==Take a picture using the Webcam==&lt;br /&gt;
&lt;br /&gt;
=Audio=&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag&lt;br /&gt;
&lt;br /&gt;
  https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
  &lt;br /&gt;
  &amp;lt;audio controls&lt;br /&gt;
    src=&amp;quot;http://media.w3.org/2010/07/bunny/04-Death_Becomes_Fur.oga&amp;quot;&amp;gt;&lt;br /&gt;
    Your user agent does not support the HTML5 Audio element.&lt;br /&gt;
  &amp;lt;/audio&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  See http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  Volume is read-only on iOS.&lt;br /&gt;
  Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
== Record sound using the microphone ==&lt;br /&gt;
&lt;br /&gt;
=Input/Touch=&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95651</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95651"/>
		<updated>2015-05-15T13:55:15Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;This page is under construction&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
    &lt;br /&gt;
  &amp;lt;video width=&amp;quot;400&amp;quot; controls&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.mp4&amp;quot; type=&amp;quot;video/mp4&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.ogg&amp;quot; type=&amp;quot;video/ogg&amp;quot;&amp;gt;&lt;br /&gt;
    Your browser does not support HTML5 video.&lt;br /&gt;
  &amp;lt;/video&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag&lt;br /&gt;
&lt;br /&gt;
  https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
  &lt;br /&gt;
  &amp;lt;audio controls&lt;br /&gt;
    src=&amp;quot;http://media.w3.org/2010/07/bunny/04-Death_Becomes_Fur.oga&amp;quot;&amp;gt;&lt;br /&gt;
    Your user agent does not support the HTML5 Audio element.&lt;br /&gt;
  &amp;lt;/audio&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  Volume is read-only on iOS.&lt;br /&gt;
  Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95650</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95650"/>
		<updated>2015-05-15T13:52:44Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;This page is under construction&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
    &lt;br /&gt;
  &amp;lt;video width=&amp;quot;400&amp;quot; controls&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.mp4&amp;quot; type=&amp;quot;video/mp4&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;source src=&amp;quot;mov_bbb.ogg&amp;quot; type=&amp;quot;video/ogg&amp;quot;&amp;gt;&lt;br /&gt;
    Your browser does not support HTML5 video.&lt;br /&gt;
  &amp;lt;/video&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  Volume is read-only on iOS.&lt;br /&gt;
  Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95620</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95620"/>
		<updated>2015-05-08T13:25:10Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Overview of HTML5 media libraries and feedbacks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;This page is under construction&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  * http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  * http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  * http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  * http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  * Volume is read-only on iOS.&lt;br /&gt;
  * Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95616</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95616"/>
		<updated>2015-05-08T11:38:00Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Warning */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  * http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  * http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  * http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  * http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO-1.5&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android 4.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS 8.X&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  * Volume is read-only on iOS.&lt;br /&gt;
  * Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95615</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95615"/>
		<updated>2015-05-08T11:37:10Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Display a Video ? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  * http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  * http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  * http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  * http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Platform&lt;br /&gt;
| MP4 Support&lt;br /&gt;
| OGV Support&lt;br /&gt;
|-&lt;br /&gt;
| XO&lt;br /&gt;
|&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|-&lt;br /&gt;
| Android&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| iOS&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | X&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  * Volume is read-only on iOS.&lt;br /&gt;
  * Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95614</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95614"/>
		<updated>2015-05-08T00:00:38Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  * http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  * http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  * http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  * http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  * Volume is read-only on iOS.&lt;br /&gt;
  * Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95613</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95613"/>
		<updated>2015-05-07T23:57:07Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Overview of HTML5 media libraries and feedbacks=&lt;br /&gt;
&lt;br /&gt;
== Display a Video ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogv and .mp4 files&lt;br /&gt;
&lt;br /&gt;
Even if ogv is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
  * http://caniuse.com/#feat=mpeg4&lt;br /&gt;
  * http://caniuse.com/#feat=ogv&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can simply use a video tag&lt;br /&gt;
&lt;br /&gt;
  * http://www.w3schools.com/html/html5_video.asp&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
On Android, &amp;gt;=2.3 is strongly recommended&lt;br /&gt;
&lt;br /&gt;
  * http://www.broken-links.com/2010/07/08/making-html5-video-work-on-android-phones/&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Play sound ? ==&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
&lt;br /&gt;
You should provide both .ogg and .mp3 files&lt;br /&gt;
&lt;br /&gt;
Even if ogg is free, it’s not supported on all majors platforms.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
You can use the audio tag - https://www.w3.org/wiki/HTML/Elements/audio&lt;br /&gt;
&lt;br /&gt;
=== Warning ===&lt;br /&gt;
&lt;br /&gt;
  * Volume is read-only on iOS.&lt;br /&gt;
  * Chrome on Android does not support autoplay as advised by the specification.&lt;br /&gt;
&lt;br /&gt;
=== Sound Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com/SoundJS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Interact with Canvas ? ==&lt;br /&gt;
&lt;br /&gt;
=== Scene Manager ===&lt;br /&gt;
&lt;br /&gt;
  * http://createjs.com&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95612</id>
		<title>HTML5MediaLibraries</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=HTML5MediaLibraries&amp;diff=95612"/>
		<updated>2015-05-07T23:22:09Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Overview of HTML5 media libraries and feedbacks&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Overview of HTML5 media libraries and feedbacks&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94920</id>
		<title>Summer of Code/2015/mohayon.SugarWebBasicActivitySet</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94920"/>
		<updated>2015-03-25T08:03:09Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About You ==&lt;br /&gt;
&#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Michaël Ohayon, I am a 4th year student at Epitech Paris&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon75@gmail.com&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your IRC nickname on irc.freenode.net?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your first 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 French, I am fluent in English.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where are you located, and what hours (UTC) 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&#039;m located in Paris, France.&lt;br /&gt;
&lt;br /&gt;
I&#039;m planning to work 17:00 - 22:00 on Monday, Tuesday and Wednesday (I got a part time job) and 10:00 - 18:00 the other days.&lt;br /&gt;
&lt;br /&gt;
&#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;
I got invested inside the french ubuntu loco team (ubuntu-fr.org) by helping during ubuntu parties.I started in October 2007 as a simple visitor and became a volunteer by helping people switching from Windows to Ubuntu.&lt;br /&gt;
Back in thoses days, migrating was not as simple as today and this was a really great human experience for me. As a longtime GNU/Linux educated user, Open-source is something really important to me. It&#039;s a way to communicate and share values with everyone.&lt;br /&gt;
&lt;br /&gt;
Now that I&#039;m a programmer, I think that I can move forward and also contribute with my programming skills.&lt;br /&gt;
&lt;br /&gt;
I attended a GSOC conference by Lionel Laské and decided to register.&lt;br /&gt;
&lt;br /&gt;
==About your project==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugar Web Basic Activity Set&lt;br /&gt;
&lt;br /&gt;
&#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? What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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;
This project is a full rewriting of some Sugar apps : Calculate, Paint, Memorize and Record using the Sugar Web Framework in order to get close to every device.&lt;br /&gt;
	Thoses apps are the basics apps that every children need to have.&lt;br /&gt;
&lt;br /&gt;
This rewriting is needed to merge apps from Sugar/Fedora and Sugarizer/Web.&lt;br /&gt;
Those apps tends to be used by every childrens using either a XO or a Web Browser. (Including PhoneGap/Cordova supported platform such as Android/iOS).&lt;br /&gt;
&lt;br /&gt;
The goal of the project is to provide the same experience for childrens ignoring the devices they are on. Moving to PhoneGap/Cordova is a really great step for Sugar, it&#039;s a way to provide the Sugar experience to every child using the web standards.&lt;br /&gt;
&lt;br /&gt;
The main technologies to be used will be &#039;&#039;&#039;HTML5 and Javascript&#039;&#039;&#039;. The ability to read the Python source code is required in order to provide the same features for the Sugar Web apps as on the XO.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;I have identified many difficults parts : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
- The abstract of the the touch/click layer in order to handle childrens using a computer with a keyboard and a mouse but also a child using a touchscreen with a phone or a tablet.&lt;br /&gt;
&lt;br /&gt;
- Responsive design in order to get a usuable app on both small and big screens&lt;br /&gt;
&lt;br /&gt;
- The storage layer which as to save the app state but also videos and pictures resources.&lt;br /&gt;
&lt;br /&gt;
- Phone compatibility which can be tricky with inputs and drawings (iOS and Android are not always acting the same way and need code customisations)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Libraries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
These are some libraries that I will look into in order to accelerate the development. The libraries are all at least MIT licensed. This is not a definitive choice, iOS and Android compatibility has to be checked.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EaselJS&#039;&#039;&#039; is a library made for working with canvas. I will definitely use it for the games development.  It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;wPaint&#039;&#039;&#039; is a jQuery plugin used to create &amp;quot;Paint like&amp;quot; apps. It has a builtin support of undo/redo. I think it&#039;s a great start for the Paint App. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RecordRTC&#039;&#039;&#039; is a Javascript-based media-recording library. I will look into this library to develop the Record app. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;JSXGraph&#039;&#039;&#039; is a Javascript library used for geometry and function plotting. I will use it for the Calc app. It is LGPL/MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Math.js&#039;&#039;&#039; is a Javascript library used for expression parsing. It will be used for the Calc app. It is Apache licensed.&lt;br /&gt;
&lt;br /&gt;
I will develop step by step using an Agile methodology.&lt;br /&gt;
&lt;br /&gt;
I have downloaded the Calculate, Paint, Memorize and Record xo files and will mimic their GUI.&lt;br /&gt;
My apps will have the same look and feel that the natives ones.&lt;br /&gt;
&lt;br /&gt;
My timeline&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Week 0 || Research Work on frameworks compatibility (phone, tablets and XO laptop located at Le Spot Bouygues)&lt;br /&gt;
|-&lt;br /&gt;
| Week 1 - 19 May || Calculate application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Base mathematical expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Results displaying and saving inside the Journal&lt;br /&gt;
|-&lt;br /&gt;
| Week 2 - 25 May || Calculate application :&lt;br /&gt;
Advanced mathematicals expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Graph support&amp;lt;br&amp;gt;&lt;br /&gt;
Ouput format controls (digits, bases)&amp;lt;br&amp;gt;&lt;br /&gt;
Input buttons for sin,cos, etc&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 3 - 1 June || Calculate application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Paint application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Basic drawing&amp;lt;br&amp;gt;&lt;br /&gt;
Color palette&amp;lt;br&amp;gt;&lt;br /&gt;
Undo / Redo&amp;lt;br&amp;gt;&lt;br /&gt;
Text typing support&amp;lt;br&amp;gt;&lt;br /&gt;
Saving to the Journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 4 - 8 June || Paint application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Memorize application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Base game context&amp;lt;br&amp;gt;&lt;br /&gt;
Grid size picker&amp;lt;br&amp;gt;&lt;br /&gt;
Default grid creation&amp;lt;br&amp;gt;&lt;br /&gt;
Ability to play the Game&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 5 - 15 June || Memorize application programming :&lt;br /&gt;
Grid creation using images, text and sound from Journal&amp;lt;br&amp;gt;&lt;br /&gt;
Grid saving to the Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Load game from journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 6 - 22 June || Memorize application programming :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Record application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Picture taking&amp;lt;br&amp;gt;&lt;br /&gt;
Publishing pictures to Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MidTerm Evaluation | MidTerm Evaluation&lt;br /&gt;
|-&lt;br /&gt;
| Week 7 - 29 June || Planning scheduling evaluation and modifications if required&lt;br /&gt;
All apps checking&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 8 - 6 July || Record application programming :&lt;br /&gt;
Sound recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Sound publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Week 9 - 13 July || Record application programming :&lt;br /&gt;
Video recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Video publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 10 - 20 July || Calc and Paint app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 11 - 27 July || Memorize and Record app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 12 - 3 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 13 -  10 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 14 - 17 August || Final patches in order to make everything working flawlessly&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#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;
I am really dedicated to my work, I can&#039;t stand doing something and not finishing it.&lt;br /&gt;
&lt;br /&gt;
I like when working really hard gets to something : my scolarity is great, my GPA is 4 (out of 4).&lt;br /&gt;
I&#039;ve led a R&amp;amp;D laboratory in my school focused on Google Technologies (Android / Dart / Angular / Go).&lt;br /&gt;
Our goal was to  keep track on the student&#039;s free projects and give them advices and workshops to discover new technologies.&lt;br /&gt;
&lt;br /&gt;
I got seen by my school and proposed to work with the GIGN on a serious project, I can&#039;t say any details but this was a great opportunity.&lt;br /&gt;
After this project, I got hired as I&#039;m now a &amp;quot;Innovation Mentor&amp;quot; for my school and keep track on students inside the national innovation lab (12 cities).&lt;br /&gt;
&lt;br /&gt;
This year I worked with big companies from Bouygues, thanks to Lionel Laské, on making innovation prototypes using new technologies such as the Google Glass or iBeacons.&lt;br /&gt;
&lt;br /&gt;
I really like to learn by myself and to discover new horizons and that&#039;s why I&#039;m writing this today. &lt;br /&gt;
My two formers internships were about Mobile and PhoneGap/Cordova using HTML5/JS. I think I can handle the amount of work of this project and contribute to the community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==You and the community==&lt;br /&gt;
&#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;
&#039;&#039;&#039;My answer : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I think this will be a great move for Sugar onto web platforms.&lt;br /&gt;
Sugarizer will allow everyone with every device to access the same user experience with the same look and feel.&lt;br /&gt;
This is really important to provide a standard way to use Sugar, essentially when kids are involved in the using. Using web standards will allow a new way for developpers to developp and for users to discovers the possibilities provided by Sugar.&lt;br /&gt;
Thoses apps are the basics apps required to make Sugarizer a really great thing to use.&lt;br /&gt;
I hope Sugarizer will allow every child, ignoring their devices to acces education through Sugarizer !&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lionel Laské :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugarizer is a way to look forward on Sugar future. But to start a real deployment with Sugarizer, we need to include inside the activities most used today by children and teachers on Sugar. More, this basic set of activities is an important source of content for other activities in Sugar ecosystem: Record activity for example will be the main source of content for Memory, Fototoon, Write or Paint activity. So this project is really a bootstrap for the development of Sugar Web.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Martin Abente Lahaye :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It&#039;s been a while since we started with JavaScript activities and I think its time that we cover such basic set of activities. Record is especially interesting as I haven&#039;t seen anything similar for the web. This would help projects such as Sugarizer to offer a more complete experience of Sugar in the web.&lt;br /&gt;
&lt;br /&gt;
&#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;
I will ask the Sugar community, friends, collegues and my school mentors to discuss with me in order to explain what my problem is.&lt;br /&gt;
&lt;br /&gt;
I think that discussion is the first step of getting new opinions and others point of view.&lt;br /&gt;
Of course I will also use my great friends, Google, StackOverflow, Github to see if somebody has encountered the same problems I did.&lt;br /&gt;
&lt;br /&gt;
&#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 think that I will setup a blog, in order to show what the project progress is. This blog will be updated with technical and non technical posts in order to allow everyone to understand what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
- I will (if it is relevant) create pages on the Sugar wiki&lt;br /&gt;
&lt;br /&gt;
- The Git commit messages will be clear and helpfull for others developpers&lt;br /&gt;
&lt;br /&gt;
- My code will be documented in order to reveal my work and progression&lt;br /&gt;
&lt;br /&gt;
- I will also use IRC to discuss with over people in order to get their opinions of the progress and or any problem I could have.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Miscellaneous==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Screenshot of the Sugar development environment&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;sugar-home-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I like to discover things, one of the best experience I had was around 2000, close to the summer when I discovered that it was possible do create things on a computer&lt;br /&gt;
&lt;br /&gt;
I remember going in the computer room and to discover Macromedia Flash. In this session we were in pairs and I really enjoyed using the software to draw stickmens.&lt;br /&gt;
&lt;br /&gt;
This really looks simple to me now that I&#039;m a programmer running on ArchLinux every day.&lt;br /&gt;
I think that we had only made 5 or 6 frames but it was animated and I found it awesome :)&lt;br /&gt;
&lt;br /&gt;
Simple things can change our perceptions and made people want to do things, I&#039;m sure that my choice of studies is really close to the education and friends I had.&lt;br /&gt;
&lt;br /&gt;
&#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;
Eveything is okay !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;Xo-and-i-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:2015 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Xo-and-i-mohayon.png&amp;diff=94919</id>
		<title>File:Xo-and-i-mohayon.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Xo-and-i-mohayon.png&amp;diff=94919"/>
		<updated>2015-03-25T08:02:37Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94918</id>
		<title>Summer of Code/2015/mohayon.SugarWebBasicActivitySet</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94918"/>
		<updated>2015-03-25T08:00:29Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About You ==&lt;br /&gt;
&#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Michaël Ohayon, I am a 4th year student at Epitech Paris&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon75@gmail.com&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your IRC nickname on irc.freenode.net?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your first 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 French, I am fluent in English.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where are you located, and what hours (UTC) 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&#039;m located in Paris, France.&lt;br /&gt;
&lt;br /&gt;
I&#039;m planning to work 17:00 - 22:00 on Monday, Tuesday and Wednesday (I got a part time job) and 10:00 - 18:00 the other days.&lt;br /&gt;
&lt;br /&gt;
&#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;
I got invested inside the french ubuntu loco team (ubuntu-fr.org) by helping during ubuntu parties.I started in October 2007 as a simple visitor and became a volunteer by helping people switching from Windows to Ubuntu.&lt;br /&gt;
Back in thoses days, migrating was not as simple as today and this was a really great human experience for me. As a longtime GNU/Linux educated user, Open-source is something really important to me. It&#039;s a way to communicate and share values with everyone.&lt;br /&gt;
&lt;br /&gt;
Now that I&#039;m a programmer, I think that I can move forward and also contribute with my programming skills.&lt;br /&gt;
&lt;br /&gt;
I attended a GSOC conference by Lionel Laské and decided to register.&lt;br /&gt;
&lt;br /&gt;
==About your project==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugar Web Basic Activity Set&lt;br /&gt;
&lt;br /&gt;
&#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? What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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;
This project is a full rewriting of some Sugar apps : Calculate, Paint, Memorize and Record using the Sugar Web Framework in order to get close to every device.&lt;br /&gt;
	Thoses apps are the basics apps that every children need to have.&lt;br /&gt;
&lt;br /&gt;
This rewriting is needed to merge apps from Sugar/Fedora and Sugarizer/Web.&lt;br /&gt;
Those apps tends to be used by every childrens using either a XO or a Web Browser. (Including PhoneGap/Cordova supported platform such as Android/iOS).&lt;br /&gt;
&lt;br /&gt;
The goal of the project is to provide the same experience for childrens ignoring the devices they are on. Moving to PhoneGap/Cordova is a really great step for Sugar, it&#039;s a way to provide the Sugar experience to every child using the web standards.&lt;br /&gt;
&lt;br /&gt;
The main technologies to be used will be &#039;&#039;&#039;HTML5 and Javascript&#039;&#039;&#039;. The ability to read the Python source code is required in order to provide the same features for the Sugar Web apps as on the XO.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;I have identified many difficults parts : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
- The abstract of the the touch/click layer in order to handle childrens using a computer with a keyboard and a mouse but also a child using a touchscreen with a phone or a tablet.&lt;br /&gt;
&lt;br /&gt;
- Responsive design in order to get a usuable app on both small and big screens&lt;br /&gt;
&lt;br /&gt;
- The storage layer which as to save the app state but also videos and pictures resources.&lt;br /&gt;
&lt;br /&gt;
- Phone compatibility which can be tricky with inputs and drawings (iOS and Android are not always acting the same way and need code customisations)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Libraries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
These are some libraries that I will look into in order to accelerate the development. The libraries are all at least MIT licensed. This is not a definitive choice, iOS and Android compatibility has to be checked.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EaselJS&#039;&#039;&#039; is a library made for working with canvas. I will definitely use it for the games development.  It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;wPaint&#039;&#039;&#039; is a jQuery plugin used to create &amp;quot;Paint like&amp;quot; apps. It has a builtin support of undo/redo. I think it&#039;s a great start for the Paint App. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RecordRTC&#039;&#039;&#039; is a Javascript-based media-recording library. I will look into this library to develop the Record app. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;JSXGraph&#039;&#039;&#039; is a Javascript library used for geometry and function plotting. I will use it for the Calc app. It is LGPL/MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Math.js&#039;&#039;&#039; is a Javascript library used for expression parsing. It will be used for the Calc app. It is Apache licensed.&lt;br /&gt;
&lt;br /&gt;
I will develop step by step using an Agile methodology.&lt;br /&gt;
&lt;br /&gt;
I have downloaded the Calculate, Paint, Memorize and Record xo files and will mimic their GUI.&lt;br /&gt;
My apps will have the same look and feel that the natives ones.&lt;br /&gt;
&lt;br /&gt;
My timeline&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Week 0 || Research Work on frameworks compatibility (phone, tablets and XO laptop located at Le Spot Bouygues)&lt;br /&gt;
|-&lt;br /&gt;
| Week 1 - 19 May || Calculate application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Base mathematical expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Results displaying and saving inside the Journal&lt;br /&gt;
|-&lt;br /&gt;
| Week 2 - 25 May || Calculate application :&lt;br /&gt;
Advanced mathematicals expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Graph support&amp;lt;br&amp;gt;&lt;br /&gt;
Ouput format controls (digits, bases)&amp;lt;br&amp;gt;&lt;br /&gt;
Input buttons for sin,cos, etc&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 3 - 1 June || Calculate application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Paint application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Basic drawing&amp;lt;br&amp;gt;&lt;br /&gt;
Color palette&amp;lt;br&amp;gt;&lt;br /&gt;
Undo / Redo&amp;lt;br&amp;gt;&lt;br /&gt;
Text typing support&amp;lt;br&amp;gt;&lt;br /&gt;
Saving to the Journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 4 - 8 June || Paint application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Memorize application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Base game context&amp;lt;br&amp;gt;&lt;br /&gt;
Grid size picker&amp;lt;br&amp;gt;&lt;br /&gt;
Default grid creation&amp;lt;br&amp;gt;&lt;br /&gt;
Ability to play the Game&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 5 - 15 June || Memorize application programming :&lt;br /&gt;
Grid creation using images, text and sound from Journal&amp;lt;br&amp;gt;&lt;br /&gt;
Grid saving to the Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Load game from journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 6 - 22 June || Memorize application programming :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Record application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Picture taking&amp;lt;br&amp;gt;&lt;br /&gt;
Publishing pictures to Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MidTerm Evaluation | MidTerm Evaluation&lt;br /&gt;
|-&lt;br /&gt;
| Week 7 - 29 June || Planning scheduling evaluation and modifications if required&lt;br /&gt;
All apps checking&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 8 - 6 July || Record application programming :&lt;br /&gt;
Sound recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Sound publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Week 9 - 13 July || Record application programming :&lt;br /&gt;
Video recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Video publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 10 - 20 July || Calc and Paint app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 11 - 27 July || Memorize and Record app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 12 - 3 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 13 -  10 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 14 - 17 August || Final patches in order to make everything working flawlessly&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#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;
I am really dedicated to my work, I can&#039;t stand doing something and not finishing it.&lt;br /&gt;
&lt;br /&gt;
I like when working really hard gets to something : my scolarity is great, my GPA is 4 (out of 4).&lt;br /&gt;
I&#039;ve led a R&amp;amp;D laboratory in my school focused on Google Technologies (Android / Dart / Angular / Go).&lt;br /&gt;
Our goal was to  keep track on the student&#039;s free projects and give them advices and workshops to discover new technologies.&lt;br /&gt;
&lt;br /&gt;
I got seen by my school and proposed to work with the GIGN on a serious project, I can&#039;t say any details but this was a great opportunity.&lt;br /&gt;
After this project, I got hired as I&#039;m now a &amp;quot;Innovation Mentor&amp;quot; for my school and keep track on students inside the national innovation lab (12 cities).&lt;br /&gt;
&lt;br /&gt;
This year I worked with big companies from Bouygues, thanks to Lionel Laské, on making innovation prototypes using new technologies such as the Google Glass or iBeacons.&lt;br /&gt;
&lt;br /&gt;
I really like to learn by myself and to discover new horizons and that&#039;s why I&#039;m writing this today. &lt;br /&gt;
My two formers internships were about Mobile and PhoneGap/Cordova using HTML5/JS. I think I can handle the amount of work of this project and contribute to the community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==You and the community==&lt;br /&gt;
&#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;
&#039;&#039;&#039;My answer : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I think this will be a great move for Sugar onto web platforms.&lt;br /&gt;
Sugarizer will allow everyone with every device to access the same user experience with the same look and feel.&lt;br /&gt;
This is really important to provide a standard way to use Sugar, essentially when kids are involved in the using. Using web standards will allow a new way for developpers to developp and for users to discovers the possibilities provided by Sugar.&lt;br /&gt;
Thoses apps are the basics apps required to make Sugarizer a really great thing to use.&lt;br /&gt;
I hope Sugarizer will allow every child, ignoring their devices to acces education through Sugarizer !&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lionel Laské :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugarizer is a way to look forward on Sugar future. But to start a real deployment with Sugarizer, we need to include inside the activities most used today by children and teachers on Sugar. More, this basic set of activities is an important source of content for other activities in Sugar ecosystem: Record activity for example will be the main source of content for Memory, Fototoon, Write or Paint activity. So this project is really a bootstrap for the development of Sugar Web.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Martin Abente Lahaye :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It&#039;s been a while since we started with JavaScript activities and I think its time that we cover such basic set of activities. Record is especially interesting as I haven&#039;t seen anything similar for the web. This would help projects such as Sugarizer to offer a more complete experience of Sugar in the web.&lt;br /&gt;
&lt;br /&gt;
&#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;
I will ask the Sugar community, friends, collegues and my school mentors to discuss with me in order to explain what my problem is.&lt;br /&gt;
&lt;br /&gt;
I think that discussion is the first step of getting new opinions and others point of view.&lt;br /&gt;
Of course I will also use my great friends, Google, StackOverflow, Github to see if somebody has encountered the same problems I did.&lt;br /&gt;
&lt;br /&gt;
&#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 think that I will setup a blog, in order to show what the project progress is. This blog will be updated with technical and non technical posts in order to allow everyone to understand what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
- I will (if it is relevant) create pages on the Sugar wiki&lt;br /&gt;
&lt;br /&gt;
- The Git commit messages will be clear and helpfull for others developpers&lt;br /&gt;
&lt;br /&gt;
- My code will be documented in order to reveal my work and progression&lt;br /&gt;
&lt;br /&gt;
- I will also use IRC to discuss with over people in order to get their opinions of the progress and or any problem I could have.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Miscellaneous==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Screenshot of the Sugar development environment&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;sugar-home-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I like to discover things, one of the best experience I had was around 2000, close to the summer when I discovered that it was possible do create things on a computer&lt;br /&gt;
&lt;br /&gt;
I remember going in the computer room and to discover Macromedia Flash. In this session we were in pairs and I really enjoyed using the software to draw stickmens.&lt;br /&gt;
&lt;br /&gt;
This really looks simple to me now that I&#039;m a programmer running on ArchLinux every day.&lt;br /&gt;
I think that we had only made 5 or 6 frames but it was animated and I found it awesome :)&lt;br /&gt;
&lt;br /&gt;
Simple things can change our perceptions and made people want to do things, I&#039;m sure that my choice of studies is really close to the education and friends I had.&lt;br /&gt;
&lt;br /&gt;
&#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;
Eveything is okay !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;xo-and-i-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:2015 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94916</id>
		<title>Summer of Code/2015/mohayon.SugarWebBasicActivitySet</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94916"/>
		<updated>2015-03-25T07:13:38Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About You ==&lt;br /&gt;
&#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Michaël Ohayon, I am a 4th year student at Epitech Paris&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon75@gmail.com&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your IRC nickname on irc.freenode.net?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your first 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 French, I am fluent in English.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where are you located, and what hours (UTC) 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&#039;m located in Paris, France.&lt;br /&gt;
&lt;br /&gt;
I&#039;m planning to work 17:00 - 22:00 on Monday, Tuesday and Wednesday (I got a part time job) and 10:00 - 18:00 the other days.&lt;br /&gt;
&lt;br /&gt;
&#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;
I got invested inside the french ubuntu loco team (ubuntu-fr.org) by helping during ubuntu parties.I started in October 2007 as a simple visitor and became a volunteer by helping people switching from Windows to Ubuntu.&lt;br /&gt;
Back in thoses days, migrating was not as simple as today and this was a really great human experience for me. As a longtime GNU/Linux educated user, Open-source is something really important to me. It&#039;s a way to communicate and share values with everyone.&lt;br /&gt;
&lt;br /&gt;
Now that I&#039;m a programmer, I think that I can move forward and also contribute with my programming skills.&lt;br /&gt;
&lt;br /&gt;
I attended a GSOC conference by Lionel Laské and decided to register.&lt;br /&gt;
&lt;br /&gt;
==About your project==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugar Web Basic Activity Set&lt;br /&gt;
&lt;br /&gt;
&#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? What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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;
This project is a full rewriting of some Sugar apps : Calculate, Paint, Memorize and Record using the Sugar Web Framework in order to get close to every device.&lt;br /&gt;
	Thoses apps are the basics apps that every children need to have.&lt;br /&gt;
&lt;br /&gt;
This rewriting is needed to merge apps from Sugar/Fedora and Sugarizer/Web.&lt;br /&gt;
Those apps tends to be used by every childrens using either a XO or a Web Browser. (Including PhoneGap/Cordova supported platform such as Android/iOS).&lt;br /&gt;
&lt;br /&gt;
The goal of the project is to provide the same experience for childrens ignoring the devices they are on. Moving to PhoneGap/Cordova is a really great step for Sugar, it&#039;s a way to provide the Sugar experience to every child using the web standards.&lt;br /&gt;
&lt;br /&gt;
The main technologies to be used will be &#039;&#039;&#039;HTML5 and Javascript&#039;&#039;&#039;. The ability to read the Python source code is required in order to provide the same features for the Sugar Web apps as on the XO.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;I have identified many difficults parts : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
- The abstract of the the touch/click layer in order to handle childrens using a computer with a keyboard and a mouse but also a child using a touchscreen with a phone or a tablet.&lt;br /&gt;
&lt;br /&gt;
- Responsive design in order to get a usuable app on both small and big screens&lt;br /&gt;
&lt;br /&gt;
- The storage layer which as to save the app state but also videos and pictures resources.&lt;br /&gt;
&lt;br /&gt;
- Phone compatibility which can be tricky with inputs and drawings (iOS and Android are not always acting the same way and need code customisations)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Libraries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
These are some libraries that I will look into in order to accelerate the development. The libraries are all at least MIT licensed. This is not a definitive choice, iOS and Android compatibility has to be checked.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EaselJS&#039;&#039;&#039; is a library made for working with canvas. I will definitely use it for the games development.  It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;wPaint&#039;&#039;&#039; is a jQuery plugin used to create &amp;quot;Paint like&amp;quot; apps. It has a builtin support of undo/redo. I think it&#039;s a great start for the Paint App. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RecordRTC&#039;&#039;&#039; is a Javascript-based media-recording library. I will look into this library to develop the Record app. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;JSXGraph&#039;&#039;&#039; is a Javascript library used for geometry and function plotting. I will use it for the Calc app. It is LGPL/MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Math.js&#039;&#039;&#039; is a Javascript library used for expression parsing. It will be used for the Calc app. It is Apache licensed.&lt;br /&gt;
&lt;br /&gt;
I will develop step by step using an Agile methodology.&lt;br /&gt;
&lt;br /&gt;
I have downloaded the Calculate, Paint, Memorize and Record xo files and will mimic their GUI.&lt;br /&gt;
My apps will have the same look and feel that the natives ones.&lt;br /&gt;
&lt;br /&gt;
My timeline&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Week 0 || Research Work on frameworks compatibility (phone, tablets and XO laptop located at Le Spot Bouygues)&lt;br /&gt;
|-&lt;br /&gt;
| Week 1 - 19 May || Calculate application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Base mathematical expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Results displaying and saving inside the Journal&lt;br /&gt;
|-&lt;br /&gt;
| Week 2 - 25 May || Calculate application :&lt;br /&gt;
Advanced mathematicals expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Graph support&amp;lt;br&amp;gt;&lt;br /&gt;
Ouput format controls (digits, bases)&amp;lt;br&amp;gt;&lt;br /&gt;
Input buttons for sin,cos, etc&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 3 - 1 June || Calculate application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Paint application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Basic drawing&amp;lt;br&amp;gt;&lt;br /&gt;
Color palette&amp;lt;br&amp;gt;&lt;br /&gt;
Undo / Redo&amp;lt;br&amp;gt;&lt;br /&gt;
Text typing support&amp;lt;br&amp;gt;&lt;br /&gt;
Saving to the Journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 4 - 8 June || Paint application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Memorize application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Base game context&amp;lt;br&amp;gt;&lt;br /&gt;
Grid size picker&amp;lt;br&amp;gt;&lt;br /&gt;
Default grid creation&amp;lt;br&amp;gt;&lt;br /&gt;
Ability to play the Game&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 5 - 15 June || Memorize application programming :&lt;br /&gt;
Grid creation using images, text and sound from Journal&amp;lt;br&amp;gt;&lt;br /&gt;
Grid saving to the Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Load game from journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 6 - 22 June || Memorize application programming :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Record application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Picture taking&amp;lt;br&amp;gt;&lt;br /&gt;
Publishing pictures to Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MidTerm Evaluation | MidTerm Evaluation&lt;br /&gt;
|-&lt;br /&gt;
| Week 7 - 29 June || Planning scheduling evaluation and modifications if required&lt;br /&gt;
All apps checking&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 8 - 6 July || Record application programming :&lt;br /&gt;
Sound recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Sound publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Week 9 - 13 July || Record application programming :&lt;br /&gt;
Video recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Video publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 10 - 20 July || Calc and Paint app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 11 - 27 July || Memorize and Record app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 12 - 3 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 13 -  10 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 14 - 17 August || Final patches in order to make everything working flawlessly&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#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;
I am really dedicated to my work, I can&#039;t stand doing something and not finishing it.&lt;br /&gt;
&lt;br /&gt;
I like when working really hard gets to something : my scolarity is great, my GPA is 4 (out of 4).&lt;br /&gt;
I&#039;ve led a R&amp;amp;D laboratory in my school focused on Google Technologies (Android / Dart / Angular / Go).&lt;br /&gt;
Our goal was to  keep track on the student&#039;s free projects and give them advices and workshops to discover new technologies.&lt;br /&gt;
&lt;br /&gt;
I got seen by my school and proposed to work with the GIGN on a serious project, I can&#039;t say any details but this was a great opportunity.&lt;br /&gt;
After this project, I got hired as I&#039;m now a &amp;quot;Innovation Mentor&amp;quot; for my school and keep track on students inside the national innovation lab (12 cities).&lt;br /&gt;
&lt;br /&gt;
This year I worked with big companies from Bouygues, thanks to Lionel Laské, on making innovation prototypes using new technologies such as the Google Glass or iBeacons.&lt;br /&gt;
&lt;br /&gt;
I really like to learn by myself and to discover new horizons and that&#039;s why I&#039;m writing this today. &lt;br /&gt;
My two formers internships were about Mobile and PhoneGap/Cordova using HTML5/JS. I think I can handle the amount of work of this project and contribute to the community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==You and the community==&lt;br /&gt;
&#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;
&#039;&#039;&#039;My answer : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I think this will be a great move for Sugar onto web platforms.&lt;br /&gt;
Sugarizer will allow everyone with every device to access the same user experience with the same look and feel.&lt;br /&gt;
This is really important to provide a standard way to use Sugar, essentially when kids are involved in the using. Using web standards will allow a new way for developpers to developp and for users to discovers the possibilities provided by Sugar.&lt;br /&gt;
Thoses apps are the basics apps required to make Sugarizer a really great thing to use.&lt;br /&gt;
I hope Sugarizer will allow every child, ignoring their devices to acces education through Sugarizer !&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lionel Laské :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugarizer is a way to look forward on Sugar future. But to start a real deployment with Sugarizer, we need to include inside the activities most used today by children and teachers on Sugar. More, this basic set of activities is an important source of content for other activities in Sugar ecosystem: Record activity for example will be the main source of content for Memory, Fototoon, Write or Paint activity. So this project is really a bootstrap for the development of Sugar Web.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Martin Abente Lahaye :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It&#039;s been a while since we started with JavaScript activities and I think its time that we cover such basic set of activities. Record is especially interesting as I haven&#039;t seen anything similar for the web. This would help projects such as Sugarizer to offer a more complete experience of Sugar in the web.&lt;br /&gt;
&lt;br /&gt;
&#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;
I will ask the Sugar community, friends, collegues and my school mentors to discuss with me in order to explain what my problem is.&lt;br /&gt;
&lt;br /&gt;
I think that discussion is the first step of getting new opinions and others point of view.&lt;br /&gt;
Of course I will also use my great friends, Google, StackOverflow, Github to see if somebody has encountered the same problems I did.&lt;br /&gt;
&lt;br /&gt;
&#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 think that I will setup a blog, in order to show what the project progress is. This blog will be updated with technical and non technical posts in order to allow everyone to understand what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
- I will (if it is relevant) create pages on the Sugar wiki&lt;br /&gt;
&lt;br /&gt;
- The Git commit messages will be clear and helpfull for others developpers&lt;br /&gt;
&lt;br /&gt;
- My code will be documented in order to reveal my work and progression&lt;br /&gt;
&lt;br /&gt;
- I will also use IRC to discuss with over people in order to get their opinions of the progress and or any problem I could have.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Miscellaneous==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Screenshot of the Sugar development environment&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;sugar-home-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I like to discover things, one of the best experience I had was around 2000, close to the summer when I discovered that it was possible do create things on a computer&lt;br /&gt;
&lt;br /&gt;
I remember going in the computer room and to discover Macromedia Flash. In this session we were in pairs and I really enjoyed using the software to draw stickmens.&lt;br /&gt;
&lt;br /&gt;
This really looks simple to me now that I&#039;m a programmer running on ArchLinux every day.&lt;br /&gt;
I think that we had only made 5 or 6 frames but it was animated and I found it awesome :)&lt;br /&gt;
&lt;br /&gt;
Simple things can change our perceptions and made people want to do things, I&#039;m sure that my choice of studies is really close to the education and friends I had.&lt;br /&gt;
&lt;br /&gt;
&#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;
Eveything is okay !&lt;br /&gt;
&lt;br /&gt;
[[Category:2015 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94900</id>
		<title>Summer of Code/2015/mohayon.SugarWebBasicActivitySet</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet&amp;diff=94900"/>
		<updated>2015-03-24T21:44:05Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: Sugar Web Basic Activity Set proposal by mohayon&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About You ==&lt;br /&gt;
&#039;&#039;&#039;What is your name?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
My name is Michaël Ohayon, I am a 4th year student at Epitech Paris&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your email address?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon75@gmail.com&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your Sugar Labs wiki username?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your IRC nickname on irc.freenode.net?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
mohayon&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is your first 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 French, I am fluent in English.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where are you located, and what hours (UTC) 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&#039;m located in Paris, France.&lt;br /&gt;
&lt;br /&gt;
I&#039;m planning to work 17:00 - 22:00 on Monday, Tuesday and Wednesday (I got a part time job) and 10:00 - 18:00 the other days.&lt;br /&gt;
&lt;br /&gt;
&#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;
I got invested inside the french ubuntu loco team (ubuntu-fr.org) by helping during ubuntu parties.I started in October 2007 as a simple visitor and became a volunteer by helping people switching from Windows to Ubuntu.&lt;br /&gt;
Back in thoses days, migrating was not as simple as today and this was a really great human experience for me. As a longtime GNU/Linux educated user, Open-source is something really important to me. It&#039;s a way to communicate and share values with everyone.&lt;br /&gt;
&lt;br /&gt;
Now that I&#039;m a programmer, I think that I can move forward and also contribute with my programming skills.&lt;br /&gt;
&lt;br /&gt;
I attended a GSOC conference by Lionel Laské and decided to register.&lt;br /&gt;
&lt;br /&gt;
==About your project==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is the name of your project?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugar Web Basic Activity Set&lt;br /&gt;
&lt;br /&gt;
&#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? What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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;
This project is a full rewriting of some Sugar apps : Calculate, Paint, Memorize and Record using the Sugar Web Framework in order to get close to every device.&lt;br /&gt;
	Thoses apps are the basics apps that every children need to have.&lt;br /&gt;
&lt;br /&gt;
This rewriting is needed to merge apps from Sugar/Fedora and Sugarizer/Web.&lt;br /&gt;
Those apps tends to be used by every childrens using either a XO or a Web Browser. (Including PhoneGap/Cordova supported platform such as Android/iOS).&lt;br /&gt;
&lt;br /&gt;
The goal of the project is to provide the same experience for childrens ignoring the devices they are on. Moving to PhoneGap/Cordova is a really great step for Sugar, it&#039;s a way to provide the Sugar experience to every child using the web standards.&lt;br /&gt;
&lt;br /&gt;
The main technologies to be used will be &#039;&#039;&#039;HTML5 and Javascript&#039;&#039;&#039;. The ability to read the Python source code is required in order to provide the same features for the Sugar Web apps as on the XO.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;I have identified many difficults parts : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
- The abstract of the the touch/click layer in order to handle childrens using a computer with a keyboard and a mouse but also a child using a touchscreen with a phone or a tablet.&lt;br /&gt;
&lt;br /&gt;
- Responsive design in order to get a usuable app on both small and big screens&lt;br /&gt;
&lt;br /&gt;
- The storage layer which as to save the app state but also videos and pictures resources.&lt;br /&gt;
&lt;br /&gt;
- Phone compatibility which can be tricky with inputs and drawings (iOS and Android are not always acting the same way and need code customisations)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Libraries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
These are some libraries that I will look into in order to accelerate the development. The libraries are all at least MIT licensed. This is not a definitive choice, iOS and Android compatibility has to be checked.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EaselJS&#039;&#039;&#039; is a library made for working with canvas. I will definitely use it for the games development.  It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;wPaint&#039;&#039;&#039; is a jQuery plugin used to create &amp;quot;Paint like&amp;quot; apps. It has a builtin support of undo/redo. I think it&#039;s a great start for the Paint App. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RecordRTC&#039;&#039;&#039; is a Javascript-based media-recording library. I will look into this library to develop the Record app. It is MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;JSXGraph&#039;&#039;&#039; is a Javascript library used for geometry and function plotting. I will use it for the Calc app. It is LGPL/MIT licensed&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Math.js&#039;&#039;&#039; is a Javascript library used for expression parsing. It will be used for the Calc app. It is Apache licensed.&lt;br /&gt;
&lt;br /&gt;
I will develop step by step using an Agile methodology.&lt;br /&gt;
&lt;br /&gt;
I have downloaded the Calculate, Paint, Memorize and Record xo files and will mimic their GUI.&lt;br /&gt;
My apps will have the same look and feel that the natives ones.&lt;br /&gt;
&lt;br /&gt;
My timeline&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| Week 0 || Research Work on frameworks compatibility (phone, tablets and XO laptop located at Le Spot Bouygues)&lt;br /&gt;
|-&lt;br /&gt;
| Week 1 - 19 May || Calculate application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Base mathematical expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Results displaying and saving inside the Journal&lt;br /&gt;
|-&lt;br /&gt;
| Week 2 - 25 May || Calculate application :&lt;br /&gt;
Advanced mathematicals expression handling&amp;lt;br&amp;gt;&lt;br /&gt;
Graph support&amp;lt;br&amp;gt;&lt;br /&gt;
Ouput format controls (digits, bases)&amp;lt;br&amp;gt;&lt;br /&gt;
Input buttons for sin,cos, etc&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 3 - 1 June || Calculate application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Paint application :&lt;br /&gt;
Base GUI, landscape mode&amp;lt;br&amp;gt;&lt;br /&gt;
Touch / clicks inputs handling&amp;lt;br&amp;gt;&lt;br /&gt;
Basic drawing&amp;lt;br&amp;gt;&lt;br /&gt;
Color palette&amp;lt;br&amp;gt;&lt;br /&gt;
Undo / Redo&amp;lt;br&amp;gt;&lt;br /&gt;
Text typing support&amp;lt;br&amp;gt;&lt;br /&gt;
Saving to the Journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 4 - 8 June || Paint application :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Memorize application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Base game context&amp;lt;br&amp;gt;&lt;br /&gt;
Grid size picker&amp;lt;br&amp;gt;&lt;br /&gt;
Default grid creation&amp;lt;br&amp;gt;&lt;br /&gt;
Ability to play the Game&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 5 - 15 June || Memorize application programming :&lt;br /&gt;
Grid creation using images, text and sound from Journal&amp;lt;br&amp;gt;&lt;br /&gt;
Grid saving to the Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Load game from journal (local or cloud)&lt;br /&gt;
|-&lt;br /&gt;
| Week 6 - 22 June || Memorize application programming :&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Record application programming :&amp;lt;br&amp;gt;&lt;br /&gt;
Base GUI&amp;lt;br&amp;gt;&lt;br /&gt;
Picture taking&amp;lt;br&amp;gt;&lt;br /&gt;
Publishing pictures to Journal (local or cloud)&amp;lt;br&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MidTerm Evaluation | MidTerm Evaluation&lt;br /&gt;
|-&lt;br /&gt;
| Week 7 - 29 June || Planning scheduling evaluation and modifications if required&lt;br /&gt;
All apps checking&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 8 - 6 July || Record application programming :&lt;br /&gt;
Sound recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Sound publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Week 9 - 13 July || Record application programming :&lt;br /&gt;
Video recording&amp;lt;br/&amp;gt;&lt;br /&gt;
Video publishing to Journal (local or cloud)&amp;lt;br/&amp;gt;&lt;br /&gt;
Testing on XO, Android, iOS, PC&amp;lt;br/&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Week 10 - 20 July || Calc and Paint app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 11 - 27 July || Memorize and Record app checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 12 - 3 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&amp;lt;br/&amp;gt;&lt;br /&gt;
Blog posts, documentation writing&lt;br /&gt;
|-&lt;br /&gt;
| Week 13 -  10 August || All apps checking&lt;br /&gt;
Bug hunting&amp;lt;br/&amp;gt;&lt;br /&gt;
Bug fixing&lt;br /&gt;
|-&lt;br /&gt;
| Week 14 - 17 August || Final patches in order to make everything working flawlessly&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#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;
I am really dedicated to my work, I can&#039;t stand doing something and not finishing it.&lt;br /&gt;
&lt;br /&gt;
I like when working really hard gets to something : my scolarity is great, my GPA is 4 (out of 4).&lt;br /&gt;
I&#039;ve led a R&amp;amp;D laboratory in my school focused on Google Technologies (Android / Dart / Angular / Go).&lt;br /&gt;
Our goal was to  keep track on the student&#039;s free projects and give them advices and workshops to discover new technologies.&lt;br /&gt;
&lt;br /&gt;
I got seen by my school and proposed to work with the GIGN on a serious project, I can&#039;t say any details but this was a great opportunity.&lt;br /&gt;
After this project, I got hired as I&#039;m now a &amp;quot;Innovation Mentor&amp;quot; for my school and keep track on students inside the national innovation lab (12 cities).&lt;br /&gt;
&lt;br /&gt;
This year I worked with big companies from Bouygues, thanks to Lionel Laské, on making innovation prototypes using new technologies such as the Google Glass or iBeacons.&lt;br /&gt;
&lt;br /&gt;
I really like to learn by myself and to discover new horizons and that&#039;s why I&#039;m writing this today. &lt;br /&gt;
My two formers internships were about Mobile and PhoneGap/Cordova using HTML5/JS. I think I can handle the amount of work of this project and contribute to the community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==You and the community==&lt;br /&gt;
&#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;
&#039;&#039;&#039;My answer : &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I think this will be a great move for Sugar onto web platforms.&lt;br /&gt;
Sugarizer will allow everyone with every device to access the same user experience with the same look and feel.&lt;br /&gt;
This is really important to provide a standard way to use Sugar, essentially when kids are involved in the using. Using web standards will allow a new way for developpers to developp and for users to discovers the possibilities provided by Sugar.&lt;br /&gt;
Thoses apps are the basics apps required to make Sugarizer a really great thing to use.&lt;br /&gt;
I hope Sugarizer will allow every child, ignoring their devices to acces education through Sugarizer !&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lionel Laské (lionel AT olpc-france.org) :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sugarizer is a way to look forward on Sugar future. But to start a real deployment with Sugarizer, we need to include inside the activities most used today by children and teachers on Sugar. More, this basic set of activities is an important source of content for other activities in Sugar ecosystem: Record activity for example will be the main source of content for Memory, Fototoon, Write or Paint activity. So this project is really a bootstrap for the development of Sugar Web.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Martin Abente Lahaye :&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mail sent, waiting for response&lt;br /&gt;
&lt;br /&gt;
&#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;
I will ask the Sugar community, friends, collegues and my school mentors to discuss with me in order to explain what my problem is.&lt;br /&gt;
&lt;br /&gt;
I think that discussion is the first step of getting new opinions and others point of view.&lt;br /&gt;
Of course I will also use my great friends, Google, StackOverflow, Github to see if somebody has encountered the same problems I did.&lt;br /&gt;
&lt;br /&gt;
&#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 think that I will setup a blog, in order to show what the project progress is. This blog will be updated with technical and non technical posts in order to allow everyone to understand what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
- I will (if it is relevant) create pages on the Sugar wiki&lt;br /&gt;
&lt;br /&gt;
- The Git commit messages will be clear and helpfull for others developpers&lt;br /&gt;
&lt;br /&gt;
- My code will be documented in order to reveal my work and progression&lt;br /&gt;
&lt;br /&gt;
- I will also use IRC to discuss with over people in order to get their opinions of the progress and or any problem I could have.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Miscellaneous==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Screenshot of the Sugar development environment&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;sugar-home-mohayon.png&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describe a great learning experience you had as a child.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I like to discover things, one of the best experience I had was around 2000, close to the summer when I discovered that it was possible do create things on a computer&lt;br /&gt;
&lt;br /&gt;
I remember going in the computer room and to discover Macromedia Flash. In this session we were in pairs and I really enjoyed using the software to draw stickmens.&lt;br /&gt;
&lt;br /&gt;
This really looks simple to me now that I&#039;m a programmer running on ArchLinux every day.&lt;br /&gt;
I think that we had only made 5 or 6 frames but it was animated and I found it awesome :)&lt;br /&gt;
&lt;br /&gt;
Simple things can change our perceptions and made people want to do things, I&#039;m sure that my choice of studies is really close to the education and friends I had.&lt;br /&gt;
&lt;br /&gt;
&#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;
Eveything is okay !&lt;br /&gt;
&lt;br /&gt;
[[Category:2015 GSoC applications]]&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=File:Sugar-home-mohayon.png&amp;diff=94898</id>
		<title>File:Sugar-home-mohayon.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=File:Sugar-home-mohayon.png&amp;diff=94898"/>
		<updated>2015-03-24T21:36:00Z</updated>

		<summary type="html">&lt;p&gt;Mohayon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Mohayon</name></author>
	</entry>
</feed>