Changes

Jump to navigation Jump to search
Line 21: Line 21:  
''(We also try to match mentors by general time zone if possible.)''
 
''(We also try to match mentors by general time zone if possible.)''
   −
I am located in Delhi, India 5:30+GMT. I'm pretty flexible in my working hours, usually tend to work late.
+
I am located in Delhi, India 5:30+GMT. I usually tend to work approximately from noon to mid night.
    
=== Have you participated in an open-source project before? ===
 
=== 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?''
 
''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 contributed to openSUSE's [http://popcorn.mapleoin.eu/ popcorn] project during GSoC 2012. Popcorn collects anonymous data about usage of RPM packages. I implemented various features including making data collection anonymous, packaging client RPM, implement a simple RESTful API, integration of client in settings user interface (YaST). Source code is available on [https://github.com/opensuse/popcorn github]. My contributions are under username axitkhurana.
+
I contributed to openSUSE's [http://popcorn.mapleoin.eu/ popcorn] project during GSoC 2012. Popcorn collects anonymous data about usage of RPM packages. I implemented various features including making data collection anonymous, packaging client RPM, implement a simple RESTful API, integration of client in settings user interface (YaST). Source code is available on [https://github.com/opensuse/popcorn github]. My contributions are under username [https://github.com/openSUSE/popcorn/commits/master?page=2 axitkhurana].
    
Also, working towards a small patch for TOR's stem library.
 
Also, working towards a small patch for TOR's stem library.
Line 74: Line 74:  
#* Utilize for the ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
 
#* Utilize for the ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
 
#* Specification for others to build on
 
#* Specification for others to build on
# Multi-language support  
+
# Multi-language support
 +
# Social login/login with Sugar account
 +
# Featured projects/galleries, similar project suggestions
      Line 84: Line 86:  
''What is the timeline for development of your project? The Summer of Code work period is June 17 - September 23; tell us what you will be working on each week.''
 
''What is the timeline for development of your project? The Summer of Code work period is June 17 - September 23; tell us what you will be working on each week.''
   −
== Project Schedule ==  
+
{| class="wikitable" |
'''Before June 17'''
+
! scope="col" width="100px" | Week
Discuss ideas with the community about the flow and User Interface of the website, finalizing the features. Learn about how Sugar Activities work, it'll be easier to integrate sharing later.
+
! scope="col" width="225px" | Tasks and resources to be used
 
+
|-
'''June 17 - June 23'''
+
| Before May 27 || Interact with the community, discuss and finalize project details like UI, flow of the website, private classroom/tutorials. Use [http://scratch.mit.edu Scratch Website] for inspiration.
 
+
|-
'''June 23th - June 29th'''
+
| May 27 - June 2 || Learn how Sugar activities work, it'll be easier to integrate sharing later.
 
+
|-
'''June 30th - July 6th'''
+
| June 3 - June 9 || Build user accounts functionality with different roles for teachers, kids and parents. Add social login and integrate with Sugar user account (django social login)
 
+
|-
'''July 7th - July 13th'''
+
| June 10 - June 16 || Work on project views, how to preview different projects, adding description, likes, comments.
 
+
|-
'''July 14th - July 20th'''
+
| June 17 - June 23 || Implement gallery creation, default gallery for liked projects. Add option for adding to new or existing gallery in Project views.
 
+
|-
'''July 21nd - July 29th'''
+
| June 23 - June 29 || Write tutorial creation / private classroom functionality. Details of this part have to finalized. For chat functionality we can use django-socketio project.<ref>https://github.com/stephenmcd/django-socketio</ref>
 
+
|-
'''July 29th- August 2nd'''
+
| June 30 - July 6 || Complete user profiles, landing pages for different users with featured projects and galleries. Add ability to *fork* projects to your profile.
Mid-term Evaluation Period
+
|-
 
+
| July 7 - July 13 || REST API to access data. Use Django Rest Framework for API. It is based on Django's class based views, APIs are fully self-describing and web browseable. <ref>http://django-rest-framework.org/</ref>
'''August 3rd - August 9th'''
+
|-
 
+
| July 14 - July 29 || Buffer time for any delays and documentation.
'''August 10th - August 16th'''
+
|-
 
+
| July 29 - August 2 || Mid-term Evaluation Period
'''August 17th- August 23th'''
+
|-
 
+
| August 3 - August 16 || Two weeks for integration with Sugar Activities. Use REST API to add options to upload project to profile from inside activity. Also add option to download projects to Sugar PC on website, similar to how play store allows option to download apps from website.
'''August 24th - August 30th'''
+
|-
 
+
| August 17- August 23 || Multi-language support <ref>https://docs.djangoproject.com/en/dev/topics/i18n/</ref>
'''August 31 - September 6'''
+
|-
 
+
| August 24 - August 30 || Add other pages like about, community guidelines, contact.
'''September 7 to September 16'''
+
|-
 
+
| August 31 - September 16 || Time reserved for unexpected delays and bug fixing.
'''September 17th''' - Soft Pencil Down date.
+
|-
 
+
| September 17 || Soft Pencil Down date.
'''September 18th - September 22rd'''
+
|}
 
  −
'''September 23rd''' - Hard Pencils Down date.
      
=== My Backround ===
 
=== My Backround ===
Line 138: Line 138:  
=== Impact on the Sugar Labs community ===
 
=== Impact on the Sugar Labs community ===
 
''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.''
 
''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.''
Kids will be able to show their creations to the world. They'll also learn more by working on each other's projects. Teachers and Activity developers can work on creating tutorials for projects.  
+
 
 +
Kids will be able to show their creations to the world. They'll also learn more by working on each other's projects. Teachers and Activity developers can work on creating tutorials for projects. Parents will be able to see what their kids have been learning and appreciate their projects there.
    +
 +
:The key is learning from each other. By sharing projects, we can share best practice, learn from each other's mistakes and successes, and in general, engage in a critical dialogue. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 13:25, 2 May 2013 (EDT)
    
=== Sugar pilot deployment ===
 
=== Sugar pilot deployment ===
 
''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?''
 
''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?''
 +
 +
It would be great if we could set up a pilot deployment at [http://www.anushruti.in/ Anushruti], which is the first school for the deaf in India in an Hi-Tech Institute of National Importance. It is situated inside my college, IIT Roorkee, and I can help with setting up by coordinating with Sugar and the school, as our student group, Information Management Group, helped with their website design. Sugar's clean collaborative platform would really improve the learning environment there.
    
=== What will you do if you get stuck on your project and your mentor isn't around? ===
 
=== What will you do if you get stuck on your project and your mentor isn't around? ===
 +
Try to solve the problem myself. If I am unable to  and if it isn't urgent, I'll send an email and work on something else. If it is I'll try to get help from other people in the community on IRC or mailing list.
    
=== Keeping the community informed about problems and questions ===
 
=== Keeping the community informed about problems and questions ===
 
''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?''
 
''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?''
 +
 
Blogging and posting weekly progress on the group with any problems.
 
Blogging and posting weekly progress on the group with any problems.
   Line 168: Line 175:  
=== Additional information ===
 
=== Additional information ===
 
''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?''
 
''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?''
 +
 +
== References ==
 +
<references />
86

edits

Navigation menu