Line 16: |
Line 16: |
| * 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? | | * 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? |
| Following are the projects I have been associated in : | | Following are the projects I have been associated in : |
− | # Bibliographic Reference Parsing : http://code.google.com/p/bibliographic-reference-parsing/ OR http://code.google.com/p/google-summer-of-code-2008-plazi/ | + | 1. Bibliographic Reference Parsing : http://code.google.com/p/bibliographic-reference-parsing/ |
− | # Foodforce2 : http://code.google.com/p/foodforce/ | + | OR http://code.google.com/p/google-summer-of-code-2008-plazi/ |
− | # AI Challenge : http://code.google.com/p/ai-challenge/ | + | 2. Foodforce2 : http://code.google.com/p/foodforce/ |
| + | 3. AI Challenge : http://code.google.com/p/ai-challenge/ |
| Apart from these projects, I have been associated closely with ILUG-D and Open Source Group in my college. | | Apart from these projects, I have been associated closely with ILUG-D and Open Source Group in my college. |
| | | |
Line 24: |
Line 25: |
| | | |
| * What is the name of your project? | | * What is the name of your project? |
− | Educational Toolkit | + | Educational Toolkit |
| * 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? | | * 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 are you making |
| + | The educational toolkit is a software to facilitate discussion in classroom with the help of technology. The software will aim |
| + | at providing teachers and students with a tool to pose problems and then compare and discuss solutions. It can also be used as |
| + | a formal testing tool for class tests and provide a better gauge of a student's progress to the teacher. |
| + | Features |
| + | # Teacher makes questions. |
| + | # Students give answers via collaboration or individually. Students split in groups and go from their individual answers to a |
| + | collaborative answer |
| + | # Teacher can review all answers later |
| + | # Teacher gives individual or group feedback |
| + | ** Who are you making it for |
| + | Primary, Secondary and Higher Secondary Students and Teachers. |
| + | ** Why do they need it |
| + | It aims to act like a tool which does not take over the job of teaching, but promotes natural class environment and will aim |
| + | to fit in the classroom environment. The software promotes better examination methods and encourages group work which is vital |
| + | in any learning environment. |
| + | ** What technologies (programming languages, etc.) will you be using? |
| + | The software is being developed in Python with emphasis on easy User Interface. The software is being developed in Python with |
| + | emphasis on easy User Interface. The software will use : PyGTK for User Interface; Telepathy and DBus Tubes for connectivity; |
| + | XML DOM API for xml |
| | | |
| * 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. |