28
edits
Changes
Jump to navigation
Jump to search
Line 38:
Line 38: − + − Line 74:
Line 73: + + + + + +
→About your project
* 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.
* 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.
May 23 Start Work
May 23 Start Work; Add QGtkSyle to KDEEdu application.
Add QGtkSyle to KDEEdu application.
May 30
May 30
* 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.
* 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.
This summer I will change my major from Electrical Engineering to Computer Engineering. The change is happening due to my increased interest in programming and open source software. My interest in software started when I took an introductory course on C programming. In this course I successfully developed programs to act as automatic teller machines, inventory databases, etc. I came to realize how useful programming knowledge is in our time. Later in my school career I took a course on Computer Organization. This course was based more on hardware but we used programming to understand the concepts. Our project for this course was to develop a program to act as a MIPS processor emulator; this emulator needed to successful process different instructions based on the MIPS datapath given to us. This would be my first experience with a large and complex program.
Eventually, I realized that most of my programming knowledge is based on developing engineering/scientific command line applications. So earlier this year I set a goal for myself to learn to use graphical toolkits. In order to learn the two major toolkits used in my experience, Qt and GTK+, I decided to help port applications between the two toolkits. This was to become my summer project, until I heard about Google Summer of Code and the KDEEdu idea from SugarLabs.
I have already decided to dedicate myself to learning the skills needed for this idea over the summer. Nonetheless, I feel that working in a structured way with professionals would be extremely beneficial. My dedication to learning these skills and help from my mentor and the community will make success for this project a reality.
====You and the community====
====You and the community====