28
edits
Changes
Jump to navigation
Jump to search
Line 56:
Line 56: − '''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.'''+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Summer of Code/2014/curiousguy13/Bulletin Board (view source)
Revision as of 09:56, 15 March 2014
, 09:56, 15 March 2014no edit summary
# A chat overlay - It would be a spatially contextual chatting interface .It would be implemented as transparent layer over an activity where one could place annotation style chat bubbles that may be placed anywhere on the screen.This would enable discussions on specific areas in an activity and in one instance a teacher could check a child's work and place these annotations on places which need improvement.
# A chat overlay - It would be a spatially contextual chatting interface .It would be implemented as transparent layer over an activity where one could place annotation style chat bubbles that may be placed anywhere on the screen.This would enable discussions on specific areas in an activity and in one instance a teacher could check a child's work and place these annotations on places which need improvement.
These tools will be implemented using python and gtk3+.
These tools will be implemented using python and gtk3+.
'''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.'''
{| class="wikitable"
|-
! Week/Days !! Work to be done
|-
| 21 April-19 May (Community Bonding Period) || Understand the existing sugar and sugar-toolkit code and discuss the design and implementation options with mentors and sugar community
|-
| 19 May-26 May (Week 1)|| Start coding the UI for chat overlay
|-
| 26 May-2 June || Work on the sharing functionality of chat overlay and improve UI
|-
| 2 June-9 June || Work on the sharing functionality of chat overlay and improve UI
|-
| 9 June- 16 June || Buffer Week
|-
| 16 June-23 June || Start coding the UI for persistent clipboard
|-
| 23 June-30 June || Mid-term Evaluation Week (Buffer week, complete remaining work)
|-
| 30 June-7 July || Work on the functionality of persistent clipboard.
|-
| 7 July-14 July|| Work on the functionality of persistent clipboard and improve UI.
|-
| 14 July-21 July ||Work on the functionality of persistent clipboard and improve UI.
|-
| 21 July-28 July|| Buffer Week
|-
| 28 July-4 August || Buffer Week
|-
| 4 August-11 August || Brushing up the code , adding tests and documentation , removing bugs.
|-
| 11 August-18 August || Evaluation Week
|}
'''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.'''
Although I haven't worked on as big a project as sugarlabs but I have been involved in many projects that are listed below:
I am good with algorithms and data structures and I like to do algorithmic puzzles on projecteuler which can be found here:
I successfully completed CS50x (on edx.org) last year in which I made a finance website using HTML/CSS ,PHP, javascript and MySQL.
https://s3.amazonaws.com/verify.edx.org/downloads/1c2174e5034f446fb0f3e0439dfb8c1a/Certificate.pdf
I also made a BMI calculator android app in Java as a final project of CS50x which can be found here:
I also successfully completed 6.001x of MIT (from edx.org) last year with 96% and created a web parser to monitor newsfeed over the internet as one of the problem sets.I cannot share it's code though due to the Honor Code that was promised by me.
https://s3.amazonaws.com/verify.edx.org/downloads/eba70bcc05ac483da493a0dde7ef9bcf/Certificate.pdf
I am really enthusiastic about being a part of such a great project and am ready to devote 50+ hours per week this summer as this will be the only big project that I will be involved with.
== You and the community ==
== You and the community ==