Summer of Code/2014/Smagnin/Music Suite

About you
My name is Simon Magnin-Feysot, i'm a french undergraduate in Computer science student at University of technology of Belfort-Montbéliard (UTBM)
 * What is your name?

My email adress is simon.magninfeysot@gmail.com
 * What is your email address?

Smagnin
 * What is your Sugar Labs wiki username?

smagnin
 * What is your IRC nickname on irc.freenode.net?

My native language is French but I'm quite comfortable in English. I'm located in France so it's UTC+1h. I work mainly the afternoon(begin at 3 o'clock p.m) and night (to 2 o'clock a.m) I've never work for FOSS before, but i use FOSS and only FOSS since 2 years, and for me, it's time to contribute for this great community. And I think it's very important to make FOSS for everythings, like software for children.
 * What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
 * 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.)
 * 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?

About your project
Th name of my project is Music Suite.
 * What is the name of your project?
 * 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?

Sugar's primary music offering, the TamTam suite, is woefully inadequate with touch interfaces. The goal of this project is to rewrite the suite to use the underlying mechanisms demonstrated in the touch-friendly Music Keyboard activity.
 * 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's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.


 * Timeline

During the community bonding period :


 * read documentation


 * learn git, I've already a basic use of git, but I think it would not be enough for this project (1 or 2 days will be enough for fix it)


 * play with music library of python.

first 2 weeks :
 * create structure in the repository


 * create a skeleton

others weeks:
 * daily report on my blog


 * 6-7 working hours per day


 * contact with my mentor twice a week or more, for his opinion of my work. (i'm always connect on IRC)

Last 3 weeks :
 * testing


 * correct possible leaks (if they had aren't seen before )


 * write the dcoumentation


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

I'm undergraduate in Computer Science, so I've done many project for my school. Lastly I've done a 3-dimensionnal chess (star trek chess : http://en.wikipedia.org/wiki/Three-dimensional_chess#Star_Trek_Tri-Dimensional_Chess) in Python3.2, it was very interessant.

Also for a progrmmaing project in my school I've implement a A* algorithm for solving a kind of Travelling Sales Problem, my group was second on fifteen groups. The most important in this contest was the optimization of the progrem. This was in Python too.

In C I've done many things for manage Bibtex files and Tex files (parsing, simply editing)

You and the community
The impact for me. It would be a great first experience in FOSS contributions, and my contributions to FOSS will be just the beginning. Also a big increase of my level for work in big project.
 * If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The impact for the sugar labs community. I will stay a contributor for sugar labs after the summer of code, Sugar labs will be my first contributions. I will be kind indebted to Sugar Labs. Sugar labs will get another contributors The community of FOSS is big and great, I think, it's not a problem to get help if i'm stuck, If I'm accepted, i will make a blog on my website : http://pike.tf/pike, and I would post a daily report of my work (what i've done, problems, new direction)
 * What will you do if you get stuck on your project and your mentor isn't around?
 * How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous
The one my greatest experience was when I was 6 years old. A friend would make with me a build with lego, but i would not share with him my lego, and we have build separely a construction, but small, and mine was very hugly. So i've decide too restart the construction but together, this time the build was just big and awesome. This day i've learnt : work together is totally better than work in competition.
 * Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle
 * Describe a great learning experience you had as a child.
 * Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?