Sugar Labs - User contributions [en]

Sugar-server Journal backup

2016-04-23T05:42:31Z

ManashRaja: /* Owner */

<noinclude>
[[Category:Feature|.]]
</noinclude>
== Summary ==

Modify the current Sugar Journal backup procedure to enable user's to maintain a permanent record of their documents on a school server.

== Owner ==
* Name: [[User:Tony| Tony Anderson]], [[User:ManashRaja| Manash Pratim Das]]

* Email: tony_anderson @ usa (dot) net, mpdmanash @ gmail (dot) com

== Current status ==
* Targeted release: TBD
* Last updated: 23 April 2016
* Percentage of completion: 0%

== Benefit to Sugar ==
The current backup system does not permit a user to save Journal objects which cause the total Journal size to exceed the available space on the XO. The proposed system will enable a backup to a school server to be limited to the size of the available store on the school server. It will provide the user with the ability to manage the size of the local datastore by deleting data files associated with Journal objects and enable them to be loaded again from the school server as needed.

== Scope ==
This feature changes code in Sugar and on the school server.

ds_backup.sh runs the ds_backup.py script on conection to the registered server. The current checks for backup frequency and network load are removed.

'registration' is removed from the menu. Registration is attempted with each schoolserver connection. The idmgr code on the school server is modified to ignore redundant registrations. Registration on only permitted to one school server. If a school server is not the one to which the registration is made, the ds_backup.py script is not run. An unregistered laptop registers with the first server it connects to. If this needs to be changed, the user can delete the server entry in the network control panel and then connect again.

The ds_backup.py script uses the datastore class to access the Journal. It opens each object. If the metadata has a Journal flag, the script checks whether the local object has been modified from the saved object (based on date). If so, the local copy is uploaded to replace the saved copy.

Note: if desired, the uploaded copy could become the prime and other copies could be kept with earlier version id.

If the object is new (no Journal metadata entry), and does not have a data file with a user-supplied title, the metadata file is uploaded to the Log directory and the local object is deleted.

If the object is new but has a data file with a user-supplied name, the metadata is shown with a 'Journal' flag and the object is uploaded to the 'Journal' folder. The metadata is marked as 'keep'.

If an object has a 'Journal' metadata field (new or existing), the script checks the 'keep' metadata field. If it is set and there is no local copy of the data file, it is downloaded from the school server. If it is not set and there is a local copy of the data file, it is deleted.

The create_user module on the server is changed to create the user directory with subdirectories: Journal and Log. A complete log of the Journal consists to the metadata files in Log plus the metadata files in Journal.

==UI Design==

Remove current registration menu item from main menu.

Use 'favorite' stars in Journal to control download and delete of local copies of data files
associated with Journal objects.

== How To Test ==
<ul>
<li>Examine current Journal display</li>
<li>Connect to school server<lli>
<li>Verify that Journal display shows 'favorite' star set on each object.</li>
<li>Verify that some Journal objects no not shown.</li>
<li>Clear favorite star on a Journal object.</li>
<li>Connect again to school server</li>
<li>Verify that data file for that Journal object is no longer available to resume.</li>
<li>Set favorite star on the object</li>
<li>Connect again to the school server</li>
<li>Verify that data file is now available to resume</li>
</ul>

== User Experience ==

Has control over data objects using space on laptop.
Has access to data objects saved on school server
Journal does not show objects not associated with a data file

== Dependencies ==

''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

This feature is to replace the current ds_backup-client. As an enhancment to the Journal, it is a feature of Sugar. There are parallel feature implementations included in GSOC 16 which may need lead to incompatiblities in the Journal view. These will neeed to be resolved as needed.

The implementation will attempt to preserve compatibility so that it can be retroactively installed on earlier Sugar versions. The documentation will specify how and to which versions this is supported.

The implementation is based on python 2.7. The developers are testing on 13.2.5 and later releases. Implementation assumes future versions of Fedora are compatible. There are no known changes to upstream modules needed at this time.

SOAS, Fedora, and Ubuntu implementations of Sugar are assumed to be compatible. Appropriate testing will be required. Dependencies such as generation of a serial-number can be included in the registration of the server by Sugar.

== Contingency Plan ==

== Documentation ==

Added to Sugar Labs identified documentation.

== Release Notes ==

Notify when feature is released.

== Comments and Discussion ==

There is need for community dicussion on the changes to the ui. There may be concern that
visible access to Journal objects created for log purposes may not be visible in the Journal.

Summer of Code/2016/Sugar Journal backup and restore

2016-04-20T07:24:56Z

ManashRaja: /* About your project */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added two features [https://github.com/sugarlabs/sugar/pull/665 1], [https://github.com/sugarlabs/sugar/pull/679 2], fixed three bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2], [https://github.com/sugarlabs/sugar/pull/682 3] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have started the following pull request.
* [https://github.com/sugarlabs/sugar/pull/665 Feature: Proxy setting]
* [https://github.com/sugarlabs/sugar/pull/679 Feature: Connect to multiple School Server easily]
* [https://github.com/sugarlabs/sugar/pull/668 BugFix: Fix custom restart message display in control panel]
* [https://github.com/sugarlabs/sugar/pull/677 BugFix: Timezone change not accepted on cancel, fixes #3093]
* [https://github.com/sugarlabs/sugar/pull/682 BugFix: Metacity on fail reaped after timeout, fixes #4958]

 

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-20T07:23:21Z

ManashRaja: /* Miscellaneous */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added two features [https://github.com/sugarlabs/sugar/pull/665 1], [https://github.com/sugarlabs/sugar/pull/679 2], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have started the following pull request.
* [https://github.com/sugarlabs/sugar/pull/665 Feature: Proxy setting]
* [https://github.com/sugarlabs/sugar/pull/679 Feature: Connect to multiple School Server easily]
* [https://github.com/sugarlabs/sugar/pull/668 BugFix: Fix custom restart message display in control panel]
* [https://github.com/sugarlabs/sugar/pull/677 BugFix: Timezone change not accepted on cancel, fixes #3093]
* [https://github.com/sugarlabs/sugar/pull/682 BugFix: Metacity on fail reaped after timeout, fixes #4958]

 

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-17T23:34:42Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added two features [https://github.com/sugarlabs/sugar/pull/665 1], [https://github.com/sugarlabs/sugar/pull/679 2], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have started the following pull request.
* [https://github.com/sugarlabs/sugar/pull/665 Feature: Proxy setting]
* [https://github.com/sugarlabs/sugar/pull/679 Feature: Connect to multiple School Server easily]
* [https://github.com/sugarlabs/sugar/pull/668 BugFix: Fix custom restart message display in control panel]
* [https://github.com/sugarlabs/sugar/pull/677 BugFix: Timezone change not accepted on cancel, fixes #3093]

 

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-17T23:34:03Z

ManashRaja: /* Miscellaneous */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added two features [https://github.com/sugarlabs/sugar/pull/665 1], [https://github.com/sugarlabs/sugar/pull/679 2], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have started the following pull request.
* [https://github.com/sugarlabs/sugar/pull/665 Feature: Proxy setting]
* [https://github.com/sugarlabs/sugar/pull/679 Feature: Connect to multiple School Server easily]
* [https://github.com/sugarlabs/sugar/pull/668 BugFix: Fix custom restart message display in control panel]
* [https://github.com/sugarlabs/sugar/pull/677 BugFix: Timezone change not accepted on cancel, fixes #3093]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-17T23:29:20Z

ManashRaja: /* About your project */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added two features [https://github.com/sugarlabs/sugar/pull/665 1], [https://github.com/sugarlabs/sugar/pull/679 2], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and two bug fixes [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Features/Proxy Settings

2016-04-17T23:17:04Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com), [[User:ManashRaja|Manash Pratim Das]]

== Current status ==

* Targeted release: 0.110
* Last updated: 2016-04-18
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=no proxy settings,
Use system proxy=let proxy be set by other means, Automatic=WPAD or PAC,
Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored in schemas (via 'Gsettings') and environment variables.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:Manual1-proxy.png|1200px]]

* Now open "www.google.com" shoud open.
:[[File:Google-proxy.png|1200px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:Auto-proxy.png|1200px]]

* Now open "www.google.com" shoud open.
:[[File:Google-proxy.png|1200px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:Wpad-proxy.png|1200px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (suppose as required by the WPAD-configuration-file)

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:Google-proxy.png|1200px]]

==Settings verification==

The proxy settings entered by user are verified before saving to prevent accidental change in proxy settings.
** For "manual" type the proxy host addresses are pinged to check for their existence.
** For "auto" type the existence of the *.pac file is checked.
If the above verification fails then the user is prompted with an alert message and option to either "Break the Internet connection" or "Reset".

* Manual proxy verification failed:
:[[File:Manual-proxy-error.png|640px]]

* Auto proxy verification failed:
:[[File:Auto-proxy-error.png|640px]]

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Auto-proxy-error.png

2016-04-17T23:16:38Z

ManashRaja:

File:Manual-proxy-error.png

2016-04-17T23:15:44Z

ManashRaja:

File:Wpad-proxy.png

2016-04-17T23:08:28Z

ManashRaja:

File:Google-proxy.png

2016-04-17T23:06:43Z

ManashRaja:

File:Auto-proxy.png

2016-04-17T23:05:43Z

ManashRaja:

File:Manual1-proxy.png

2016-04-17T23:03:57Z

ManashRaja:

File:Manual-proxy.png

2016-04-17T22:57:34Z

ManashRaja:

Features/Multiple schoolserver registration

2016-04-17T22:23:16Z

ManashRaja: /* How To Test */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: 0.110
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present1.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified1.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
* Connect to XSCE network. Enter its server_address in the "Server" entry present in "Network" section of control panel and click "Connect to server" from the desktop.
* If registration was successful, use Terminal activity for the command: ssh xsce-admin@server_address . Expected behavior: It will prompt for server password.
* Connect to a different XSCE network and register to it as above.
* Try doing ssh again for this XSCE. Expected behavior: It will still prompt for password, without showing identity mis-match error in case the server_address of both XSCE are same.

== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

Your comments are very welcome. Please discuss through the mailing list.

* First discussion on the mailing list:
http://lists.sugarlabs.org/archive/sugar-devel/2016-April/051805.html

Features/Multiple schoolserver registration

2016-04-17T22:18:04Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: 0.110
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present1.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified1.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
* Connect to XSCE network. Enter its server_address in the "Server" entry present in "Network" section of control panel and click "Connect to server" from the desktop.
* If registration was successful, use Terminal activity for the command: ssh xsce-admin@server_address . Expected behavior: It will prompt for server password.
* Connect to a different XSCE network and register to it as above.
* Try doing ssh again for this XSCE. Ecpected behavior: It will still prompt for password, without showing identity mis-match error in case the ip-address of both XSCE are same.
*

== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

Your comments are very welcome. Please discuss through the mailing list.

* First discussion on the mailing list:
http://lists.sugarlabs.org/archive/sugar-devel/2016-April/051805.html

Features/Multiple schoolserver registration

2016-04-17T21:49:40Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: 0.110
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present1.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified1.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multiple schoolserver registration

2016-04-17T21:27:05Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present1.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified1.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

File:Sugar-server-modified1.png

2016-04-17T21:26:54Z

ManashRaja:

File:Sugar-server-present1.png

2016-04-17T21:26:18Z

ManashRaja: Modified

Modified

File:Sugar-server-modified.png

2016-04-17T21:24:28Z

ManashRaja: ManashRaja uploaded a new version of File:Sugar-server-modified.png

File:Sugar-server-present.png

2016-04-17T21:24:12Z

ManashRaja: ManashRaja uploaded a new version of File:Sugar-server-present.png

File:Sugar-server-modified.png

2016-04-17T21:21:49Z

ManashRaja: ManashRaja uploaded a new version of File:Sugar-server-modified.png

Features/Multiple schoolserver registration

2016-04-17T21:13:22Z

ManashRaja: /* Detailed Description */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multiple schoolserver registration

2016-04-17T21:09:46Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Percentage of completion: 90%

== Detailed Description ==
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. [As discussed here http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html]
The present system for registering a Sugar laptop with an school server is depicted below. 
[[File:Sugar-server-present.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Each laptop will have same backup url and backup path (in XSCE:/library/users) for a particular XSCE as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XSCE where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups. (This is only supported in XSCE due to the presence of xs-authserver)
**No extra input is required from the user. The user just has to connect to the school server network, specify the jabber-server address and click on "Connect to server"

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to school server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
* Also no change is required on the school server side.
* Use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multi XS-server registration

2016-04-17T20:36:52Z

ManashRaja: ManashRaja moved page Features/Multi XS-server registration to Features/Multiple schoolserver registration: Replaced XS with schoolver on title

#REDIRECT [[Features/Multiple schoolserver registration]]

Features/Multiple schoolserver registration

2016-04-17T20:36:51Z

ManashRaja: ManashRaja moved page Features/Multi XS-server registration to Features/Multiple schoolserver registration: Replaced XS with schoolver on title

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Easily hop between multiple XS servers. Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 16 April 2016
* Status: Being discussed and draft developed [https://github.com/ManashRaja/sugar/commit/660985d2183416cd3ed758095e92adf82f87a10c link]


== Detailed Description ==
When a user wants to register to a new XS server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an XS server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here].
The present system for registering a Sugar laptop with an XS server is depicted below. 
[[File:Sugar-server-present.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
**No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to XS server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* the changes only affect use of Sugar with compatible school servers, such as XS or XSCE,
* use of Sugar without a school server shall not be affected.

==UI Design==
The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Proxy Settings

2016-04-15T21:50:34Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com), [[User:ManashRaja|Manash Pratim Das]]

== Current status ==

* Targeted release: Unspecified
* Last updated: 2016-04-12
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=no proxy settings,
Use system proxy=let proxy be set by other means, Automatic=WPAD or PAC,
Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored in schemas (via 'Gsettings') and environment variables.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Multiple schoolserver registration

2016-04-15T21:46:50Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Easily hop between multiple XS servers. Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 16 April 2016
* Status: Being discussed and draft developed [https://github.com/ManashRaja/sugar/commit/660985d2183416cd3ed758095e92adf82f87a10c link]


== Detailed Description ==
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path on non-XO laptops.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here].
The present system for registering a Sugar laptop with an XS server is depicted below. 
[[File:Sugar-server-present.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
**No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to XS server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
The user does not have to provide any extra input. He/she has to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Server" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multiple schoolserver registration

2016-04-15T02:46:20Z

ManashRaja: /* Detailed Description */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Easily hop between multiple XS servers. Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 15 April 2016
* Status: Being discussed and development started


== Detailed Description ==
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. Every new registration changes the serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here].
The present system for registering a Sugar laptop with an XS server is depicted below. 
[[File:Sugar-server-present.png|1000px]] 

This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature: 
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
**No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to XS server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
The user does not have to provide any extra input. He/she has to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Server" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multiple schoolserver registration

2016-04-15T02:43:46Z

ManashRaja: /* Detailed Description */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Easily hop between multiple XS servers. Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 15 April 2016
* Status: Being discussed and development started


== Detailed Description ==
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. Every new registration changes the serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here])
The present system for registering a Sugar laptop with an XS server is depicted below.
[[File:Sugar-server-present.png|1000px]]

*This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature:
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
*No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to XS server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
The user does not have to provide any extra input. He/she has to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Server" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Multiple schoolserver registration

2016-04-15T02:43:26Z

ManashRaja:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]

</noinclude>

== Summary ==
Easily hop between multiple XS servers. Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.

== Owner ==
* Name: [[User:ManashRaja| Manash Pratim Das]]

* Email: mpdmanash@gmail.com

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: 15 April 2016
* Status: Being discussed and development started


== Detailed Description ==
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. Every new registration changes the serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path.

Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here])
The present system for registering a Sugar laptop with an XS server is depicted below.
[[File:Sugar-server-present.png|1000px]]

*This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature:
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
*No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.

== Benefit to Sugar ==
This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
The feature is supposed to bring Sugar closer to XS server and improve the user experience.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
The user does not have to provide any extra input. He/she has to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Server" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug]

== Dependencies ==
None



== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

File:Sugar-server-modified.png

2016-04-15T02:10:57Z

ManashRaja:

File:Sugar-server-present.png

2016-04-15T01:41:12Z

ManashRaja:

Features/Multiple schoolserver registration

2016-04-15T01:40:34Z

ManashRaja: Created page with "<noinclude> Category:Feature Page Incomplete . <!-- You can add categories to tie features back to real deployments/schools requesting them, for examp..."

Features/Proxy Settings

2016-04-15T01:11:27Z

ManashRaja: /* Owner */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:ManashRaja|Manash Pratim Das]], [[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: Unspecified
* Last updated: 2016-04-12
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=no proxy settings,
Use system proxy=let proxy be set by other means, Automatic=WPAD or PAC,
Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored in schemas (via 'Gsettings') and environment variables.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

User:ManashRaja

2016-04-15T01:10:34Z

ManashRaja:

;Country:
:India
;Timezone:
:IST (UTC+530)
;IRC nickname:
:ManashRaja
;Contact Details
:[http://manashpratim.in/ My homepage]
:[https://github.com/ManashRaja Github]

User:ManashRaja

2016-04-15T01:10:14Z

ManashRaja:

On FreeNode and OFTC my IRC nick is silbe.
;Country:
:India
;Timezone:
:IST (UTC+530)
;IRC nickname:
:ManashRaja
;Contact Details
:[http://manashpratim.in/ My homepage]
:[https://github.com/ManashRaja Github]

User:ManashRaja

2016-04-15T01:09:46Z

ManashRaja: Created page with "Please see [http://manashpratim.in/ my homepage] for contact information. You can also send emails to my sugarlabs.org and activitycentral.com accounts (silbe@). On FreeNode a..."

Please see [http://manashpratim.in/ my homepage] for contact information. You can also send emails to my sugarlabs.org and activitycentral.com accounts (silbe@).
On FreeNode and OFTC my IRC nick is silbe.
;Country:
:India
;Timezone:
:IST (UTC+530)
;IRC nickname:
:ManashRaja
;Contact Details
:[http://manashpratim.in/ My homepage]
:[https://github.com/ManashRaja Github]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-12T04:32:59Z

ManashRaja: /* Miscellaneous */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a [https://github.com/sugarlabs/sugar/pull/665 new feature], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and two bug fixes [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-04-12T04:30:55Z

ManashRaja: /* About your project */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a [https://github.com/sugarlabs/sugar/pull/665 new feature], fixed two bugs [https://github.com/sugarlabs/sugar/pull/668 1], [https://github.com/sugarlabs/sugar/pull/677 2] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Features/Proxy Settings

2016-04-12T02:15:09Z

ManashRaja: /* Current status */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: Unspecified
* Last updated: 2016-04-12
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=no proxy settings,
Use system proxy=let proxy be set by other means, Automatic=WPAD or PAC,
Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored in schemas (via 'Gsettings') and environment variables.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2016-04-12T02:14:02Z

ManashRaja:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.99
* Last updated: 2013-02-17
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=no proxy settings,
Use system proxy=let proxy be set by other means, Automatic=WPAD or PAC,
Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored in schemas (via 'Gsettings') and environment variables.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T16:49:39Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced Sugar-server integration to increase the utility of available servers (XSCE or cloud). The following are the features in detail:
#'''Add selective backup-restore:''' (Difficulty level: easy). User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why?
#*Backups will be specific and save unnecessary wastage of storage space.
#*Teachers will be able to distribute specific Journal objects without hampering the existing Journal of a student.
#'''Add system to backup and restore from school servers (XSCE):''' (Difficulty level: medium). Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*If the school-servers are present, then they can be made an easy way to store and distribute backups among many.
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#'''Add cloud service:''' (Difficulty level: easy). In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support the "One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#'''Easy sharing of Journal items based on above server frameworks:''' (Difficulty level: medium) When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. Why?
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Use the servers for sharing storage space:''' (Difficulty level: hard). The data created by a Journal may take the free storage space on a low storage device pretty soon. Hence this background feature will let the Journal utilize both the local storage and the server storage. Journal objects or libraries will be shifted if it can be shifted to the server. When any object will be needed, it will be downloaded and cached temporarily on the local storage. A method will be devised that will be looking for the objects that can be shifted to the server like, objects which are rarely used and those containing library items. The user will be able to set rules to manage the behaviour.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Complete the specific backup-restore(1) and cloud server backup(3) features as I have a head start on both, having gone through the code and tested the functionality. [https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1], [https://github.com/ManashRaja/cloud-sync-demo 2].
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*As I would have already installed the XSCE server at my place, and the implementation discussed to its detail in the "Community bonding period" hence I believe that I can buckle up and finish at least the basic functionality of this feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 6 June-12 June
| Since, the feature "servers for sharing storage space"(5) is a difficult task, hence I have planned more time for this feature. I will create the basic functionality as per the road map we would have discussed in the "Community Bonding period"
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the 5th feature.
*Testing and code documentation.
*90% as per functionality of the project will be complete before the Mid-Term Evaluation.
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Will add more finishing touches to the features (1,2,3,5) developed above.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a [https://github.com/sugarlabs/sugar/pull/665 new feature], fixed a [https://github.com/sugarlabs/sugar/pull/668 bug] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T05:01:20Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced backup-restore, cloud sync and easy sharing features for the Sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. Teachers will be able to distribute tutorials on activities without hampering the existing Journal a student.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running Sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*"One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#*The OLPC’s new “Infinity” modular computer. A student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoC being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a [https://github.com/sugarlabs/sugar/pull/665 new feature], fixed a [https://github.com/sugarlabs/sugar/pull/668 bug] and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T04:57:31Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and restore

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

My project will add advanced backup-restore, cloud sync and easy sharing features for the Sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. Teachers will be able to distribute tutorials on activities without hampering the existing Journal a student.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running Sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*"One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#*The OLPC’s new “Infinity” modular computer. A student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoc being my top priority (8-9 hours a day and around 60 hours a week for 12 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a new feature, fixed a bug and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T04:07:35Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and Restore

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

My project will add advanced backup-restore, cloud sync and easy sharing features for the Sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. Teachers will be able to distribute tutorials on activities without hampering the existing Journal a student.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running Sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*"One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#*The OLPC’s new “Infinity” modular computer. A student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ (GTK3) for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoc being my top priority (8-9 hours a day and around 60 hours a week for 9 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a new feature, fixed a bug and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T04:04:24Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and Restore

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

My project will add advanced backup-restore, cloud sync and easy sharing features for the Sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. Teachers will be able to distribute tutorials on activities without hampering the existing Journal a student.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running Sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*"One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#*The OLPC’s new “Infinity” modular computer. A student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoc being my top priority (8-9 hours a day and around 60 hours a week for 9 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a new feature, fixed a bug and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T04:02:22Z

ManashRaja:

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization. Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and Restore

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

My project will add advanced backup-restore, cloud sync and easy sharing features for the Sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. Teachers will be able to distribute tutorials on activities without hampering the existing Journal a student.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running Sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*"One to many concept" that can be implemented on Sugar. (concept discussed on GSoC 2016 idea page [https://wiki.sugarlabs.org/go/Summer_of_Code/2016 link])
#*The OLPC’s new “Infinity” modular computer. A student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with each other in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language (its written on) or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoc being my top priority (8-9 hours a day and around 60 hours a week for 9 weeks) towards my contribution. Even though my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the Sugar code base since February 1st, added a new feature, fixed a bug and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of Sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself by trying Google search as always and referring other resources. But if in case help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated in many competitions upto the national level.

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

Yes, I would like to tell why I chose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take our laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]

Summer of Code/2016/Sugar Journal backup and restore

2016-03-25T03:42:38Z

ManashRaja: /* About You */

== About You ==
'''What is your name?'''

My name is Manash Pratim Das. I am a 2nd Year, Bachelor of Technology (B.Tech), undergraduate student at the [http://www.iitkgp.ac.in/ Indian Institute of Technology, Kharagpur, India]

'''What is your email address? '''

My email address is mpdmanash@gmail.com

'''What is your Sugar Labs wiki username?'''

ManashRaja

'''What is your IRC nickname on irc.freenode.net?'''

ManashRaja

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

My native language is Hindi, but I am fluent in English as well.

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

I live at in Kharagpur, West Bengal, India. 
My timezone is UTC + 5:30 (Indian Standard Time) 
I generally tend to work in the evening (from 5 pm) and late night (to 4 am). But my time table is very flexible and can be changed as per the convenience of my mentor/community members.

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

Yes, I have contributed to two completely open source research projects at my college:
* [https://github.com/quadrotor-IITKgp “Aerial Robotics Kharagpur”]: I am a software team member of this organization.Few specific (other than open code contribution) [https://github.com/quadrotor-IITKgp/grid_localization 1][https://github.com/ManashRaja/quad_simulator 2]
* [https://github.com/AGV-IIT-KGP “Autonomous Ground Vehicle”]: Specific work [https://github.com/AGV-IIT-KGP/computer_vision/pull/28 1],[https://github.com/AGV-IIT-KGP/eklavya-2015/pull/75 2]
* My [https://github.com/ManashRaja/ GitHub profile] in general.
I also solved a bug for an Arduino library, but it was solved before I could send the PR :) .

== About your project ==
'''What is the name of your project?'''

Sugar Journal backup and Restore

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

My project in short will add advanced backup-restore, cloud sync and easy sharing features for the sugar journal. The following are the features in detail:
#'''Add selective backup-restore:''' User can select part of the journal to be backed up or restored directly from within the backup page. Metadata for each Journal entry will store the list of dependencies and library objects, which will be downloaded again as needed (and, as available). Why? Backups will be specific and save unnecessary wastage of storage space. Replace the ineffective way to store Journal images with the risk of running out of local space. It will enable specific journal entries to be distributed by the teachers as tutorials without hampering the existing Journal of students.
#'''Add system to backup and restore from school servers (XSCE):''' Now backup can only be stored and restored from devices, but this feature will add school servers to the options. Why? 
#*The existing (ds-backup) option on OLPC OS is not an effective method because it cannot be easily restored. (from what I understand)
#*As school servers are the best common node for all the local hardware running sugar, hence storing backups at such common location will increase its accessibility by many fold.
#*The backups can be used by multiple types of hardware/platform running Sugar (OLPC pcs, Android, Sugarizer) seamlessly using school-server’s multi-platform support to the advantage.
#*Teachers can distribute journal entries on mass scale.
#'''Add cloud service:''' In a few clicks, it will let schools to connect each student’s pc to a local cloud server or a third party cloud server as per the availability to sync the journal data at a central location. Why? It will be easy for schools to let hardware be shared among the student batches as students can login to their account from any hardware and can still access his/her own journal. This feature will strongly support:
#*One to many concept that can be implemented on Sugar.
#*The OLPC’s new “Infinity” modular computer. The student’s personal setup (Journal) becomes another module.
#'''Easy sharing of Journal items based on above server frameworks:''' When server frameworks like XSCE and cloud are available, their utility can be increased by adding features where children can share any item with others in just few easy clicks. The GUI will be indifferent to the framework being used in the background even though it will provide options, if both are present at the same time.

Technologies: I will use python and its libraries for the main backend along with GTK+ for the GUI and graphics generator like Inkscape for the icons. For the different server integration, I am planning to use use server specific cli, apis, libraries or scripts like “owncloudcmd” for ownCloud, “RClone” that supports many cloud services like Google Drive, Amazon S3, Openstack Swift / Rackspace cloud files / Memset Memstore, Dropbox, Google Cloud Storage, Amazon Cloud Drive, Microsoft One Drive, Hubic, Backblaze B2, Yandex Disk, The local filesystem and tools like rsync for XSCE school-servers. I will also use polkit for permissions and symbolic links. If I finally use rclone for cloud sync, then I might learn and use go programming language in which it is made or use pexpect to run its cli.

'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; 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 (end of 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"
! style="text-align: center;" | Week
! Scheduled Work
! Time I can devote
|-
| 22 April-22 May
(Community Bonding period)
|
*Introduce and become part of the community.
*Look for various different ways to approach the project.
*Discuss with mentor(s), OLPC members, XSCE members and if possible the people who work down there to tailor the project to the perfect needs and flow.
*Draw a detailed roadmap on how I will implement each feature.
*Learn any required skill I may be missing.
*Design GUI according to the flow as discussed above and create icons as required required.
*Install XSCE and ownCloud servers at my own place.
*Create accounts in the third party cloud providers.
|22 April-29 April: 9 hours per week (end semester examinations.)
30th April-22nd May: 65 hours a week (summer vacations)

|-
| 23 May-29 May
|
*Continue the development of the selective backup-restore feature on which I already have done some work.[https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 link] I plan to finish at least 90% of this feature on this week.
*Try to match my style of coding with the existing code by reviews and proper study of the code.
|60 hours a week (summer vacations)

|-
| 30 May-5 June
|
*Complete the basic functionality of the specific and multiple backup-restore
*Start implementing and coding for making the XSCE server as backup destination and restore source.
*Build up the coding pace
|60 hours a week (summer vacations)

|-
| 6 June-12 June
|
*Finish off the XSCE server feature.
*Relatively free week to act as buffer if required or start the next week's work.
|60 hours a week (summer vacations)

|-
| 13 June-20 June
|
*Finalize the cloud integration for ownCloud and majority of the third party providers like (Google Drive, Dropbox, Amazon S3), whose prototype has been made by me already [https://github.com/ManashRaja/cloud-sync-demo link].
*Testing and code documentation
*90% as per functionality of the project will be complete
|60 hours a week (summer vacations)

|-
| 21 June-28 June
|
*Mid-Term Evaluation
*Keep on brainstorming for GUIs and integration of my project which makes it very effective and user friendly.
|

|-
| 28 June-3 July
|
*Work on the feedback received after the evaluation.
*Complete cloud integration for third party service providers for it any of them were left.
|60 hours a week (summer vacations)

|-
| 4 July-10 July
|
*Understand all types of collaborations that happen in the school among the children(students) and teachers, to know how my sharing feature fits in.
*Start coding for the sharing feature.
|60 hours a week (summer vacations)

|-
| 11 July-16 July
|
*Finish the sharing feature.
*Apart from the regular updates to the community about the project, I will submit my work upto now for review and suggestions by the community.
*Work on the suggestions.
|60 hours a week (summer vacations)

|-
| 18 July-24 July
| Buffer week to complete if work is pending or add GUI to use the cloud framework developed to support “One hardware to many user” feature of Sugar.
|60 hours a week (summer vacations)

|-
| 25 July-31 July
|
*Finalize the code
*Testing and improvements
|40 hours a week (college)

|-
| 1st Aug-7 Aug
|
*Testing and improvements
*Proper code documentation, cleanup and flake8 verification.
|40 hours a week (college)

|-
| 8 Aug-15 Aug
|
*Testing and improvements
*Feature documentation on https://wiki.sugarlabs.org/go/Features
|40 hours a week (college)

|-
| 16 Aug-24 Aug
| Submit code and evaluations.
|
|}

'''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.'''

My strength lies in my dynamic learning and self motivated hard work. I am a 2nd year undergraduate of the Indian Institute of Technology, Kharagpur where I am actively involved with the tech community and contribute to 2 research groups ([http://quadrotor-iitkgp.github.io/ 1][http://www.agv.iitkgp.ac.in/ 2]), 2 tech societies([https://www.robotix.in/team/ 1]), projects under professors and have participated in many competitions and hackathons apart from keeping my academics up. In these two years of my stay, I have learnt a great deal about time management. All the professional level work we do has made me to realize realistic timelines for myself and my team. Though I failed initially, but I am getting better. My work has been mostly in software RnD and autonomous robotics and hence I have gained lots of experience about the process and its time consumption involved in converting an idea to finished product. So, I have learned to plan my work and execute it efficiently.
Another important fact is that my college summer vacations lie in the period of 29th April to 24th July, during which I will be able to devote 100% of my work time as GSoc being my top priority (8-9 hours a day and around 60 hours a week for 9 weeks) towards my contribution. Even though I my college semester will start from 25th July, I will still be able to devote 40 hours a week due to a light semester. I also have a head start on the project I would be working on as I have been involved with the sugar code base since February 1st, added a new feature, fixed a bug and have made the prototype of two features ([https://github.com/ManashRaja/sugar/commit/e186d37182be8baf2feff0c6e3726a5e1b3753b6 1][https://github.com/ManashRaja/cloud-sync-demo 2]) I will develop in this project apart from discussion about the project on IRC. Hence I am confident that I can ensure fully dedicated work and a pledge to deliver more than I promise.

== '''You and the 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.'''

My project will mostly be used in the deployment side of sugar. I strongly believe that my project will add to the sweetness of Sugar to make it come closer to the people who deploy and the even sweeter kids who use it. Backup and restore is a very important feature for various other members of the community who might be testing, developing and integrating Sugar on multiple platforms.

'''What will you do if you get stuck on your project and your mentor isn't around?'''

If I am stuck anywhere, then I will put my best efforts to solve the problem myself, trying Google search as always and other resources. But if help is required and my mentor is not available then I would refer to the community over developer mailing list, IRC, other GSoC participant if relevant or some specific member(s) whom I might know during the course of the project (eg: Quozl`and SAMdroid who have helped me before). If the problem is not Sugar specific, then I may even take help from my tech circle (Kharagpur Open Source Society) consisting of very smart people or professors if they are available during the vacation.

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

*I would propose a repetitive scheduled meeting every two days at a particular time or as per the convenience of mentors/community members where we would discuss the progress made and the further course of action. I can understand its effectiveness as we use this technique at our college while doing projects under professors so that the focus and progression is maintained.
*I will frequently update my progress and milestones achieved on my [http://manashpratim.in/ blog].
*Share it along with doubts or queries on a particular thread for this project on the developer mailing list to welcome inputs from all the community members.

===Miscellaneous===
* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
** 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 "logout". 
[[File:Buddy-menu-manash.png|1000px]] 

''' Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. '''
:: It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

Yes I have sent two pull request. [https://github.com/sugarlabs/sugar/pull/665 Proxy setting feature] and [https://github.com/sugarlabs/sugar/pull/668 Bug fix]

* If you plan to work on Sugar-Web projects we want to be sure that you're familiar with web technologies, so:
** Clone the [https://github.com/llaske/Sugarizer Sugarizer repository]
** Using instructions [https://github.com/llaske/Sugarizer#create-your-own-activity here] develop your first Sugar-Web activity
** Send us a screenshot of your new activity executed in Sugarizer
''' Describe a great learning experience you had as a child.'''

I can relate to the goals of Sugar, now when I have grown up, since I have witnessed how an access to computer aided learning and quick access to resources (internet) can accelerate the process of learning as in my case. The ability to create has been the major driving force of my learning. Three events in particular were the most significant that I would like to share with:
*An investment into the future for a PC made by my parents at my 3rd grade gave me my best friend and teacher at my childhood. I believe, it is more about the enhancement of thinking process than in the ability to score higher marks in exams. Even though some people might be skeptical about the results of OLPC and Sugar provided the investment, but I believe in its long term effect as I have seen it.
*Then I was introduced to programming and the Internet by my school at 6th grade. The introduction made all the neurons light up in excitement for the ability to create my own real world applications.
*I was shown the path and I started sprinting on it myself. From the period of 7th grade to 10th grade, I learnt C++, C#, PHP, HTML, CSS, electronics and embedded programming to create many software and hardware applications and participated upto national level of competitions.

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

Yes, I would like to tell why I choose to contribute to Sugar. While looking at various organizations at the 2015 GSoC page, I shortlisted a few organizations based on my strongest skill set. I looked upon for the problem statement of each of the organizations that they were trying to achieve and there I came to know about Sugar. I felt attached to the community due to the following points:
*I could relate the computer aided Sugar pedagogy with my own experience.
*I am a volunteer at “National Service Scheme” in my college and along with my unit, we provide community service at a nearby village. Hence I can visualize if not perfectly the effect of OLPC and Sugar would have in the children deep down there. We used to take out laptops to show them animated content, fascinate them with electronics and RC planes. They used to gather around us and we witnessed maximum attendance on the Saturdays we went there.
*I found the community members at IRC and developer mailing list very welcome and I feel excited about my first experience at an International selfless open source project.

Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.

[[Category:2016 GSoC applications]]