KDEEdu

About you

1. What is your name?

Yazen Ghannam

1. What is your email address?

yghannam7388@gmail.com

1. What is your Sugar Labs wiki username?

yghannam7388

1. What is your IRC nickname?

yghannam7388

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

English

1. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)

Orlando, Florida, USA. GMT -4 
I usually work in the evenings, from 5pm to 11pm.

1. Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?

I am a new member of the Ubuntu Bugsquad.
https://launchpad.net/~yghannam7388

About your project

• What is the name of your project?

KDEEdu

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

There are a number of educational applications available on the K Desktop Environment. Sugar, having education in mind, would like to use these applications. The only problem is that these applications are written for KDE using the Qt toolkit, while Sugar uses the GTK+ toolkit. Therefore for Sugar to have access to these applications they must be rewritten using the GTK+ toolkit.

I plan on rewriting an appication using gtkmm instead of GTK+. My reasoning is that gtkmm and Qt are both based on the C++ programming language and should share many of the same development techniques(object-oriented, etc.). GTK+, on the other hand, is based on the C programming lanuage and techniques (functional, etc.). Using gtkmm should prove to be a smoother transition.

One experience that was lacking in my early education was the use of computers to solve math problems. You could always use a word processor to type a report or the internet to find a map for geography but you always needed to solve math problems out my hand. Therefore, I would like to "sugarize" a mathematics application from KDEEdu, probably KAlgebra since it is general purpose and has graphing capabilites. I believe this will help all students, but especially those who may find it hard to visualize some concepts.

• What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
• Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

You and the community

1. 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.
2. Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
3. What will you do if you get stuck on your project and your mentor isn't around?
4. 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

An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.

1. We want to make sure that you can set up a development environment before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.
2. What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
3. Describe a great learning experience you had as a child.
4. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?

Note: you will post this application on the wiki in the category Category:2009 GSoC applications. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list(s) (primarily sugar-devel for technical issues and It's An Education Project for educational issues) and/or IRC.

The NeL project has some good general recommendations for writing proposals. We endorse them all; although Sugar is (regrettably) not test driven development (yet - your project could change that!), we encourage GSoC code to include tests.