102
edits
Changes
Summer of Code/2016/SugarJournalSaveOption UtkarshT (view source)
Revision as of 17:41, 23 March 2016
, 17:41, 23 March 2016→About your project
* 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.
*''' 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. '''
!Task
!Task
|-
|-
|31 April to 9 May
|24th April to 9th May
|
|
* Get thorough with Journal code. Analyze its working. I have basic understanding of the code because of my previous contributions to sugar.
* Community bonding period. Gain consensus of the community on the designs and UI of the proposed features.
* Understand the working of Sugar codebase ( I already have some handson experience with Sugar)
* Discuss the specifications of all the features proposed with Mr.Tony Anderson and other community members.
|-
|-
|10 May to 18 May
|10th May to 30th May
|
|Start developing 'save as' alert popup.
* Analyze more on how collaboration works in sugar.
* Write a new alert popup module wrapped over Alert class of Suga-toolkit-gtk3.
* Develop an outline of the project and more discussion with my mentor Sam and other community members regarding the features that are to be implemented.
* Integrate the alert module to the Sugar activity base class.
* Code the automatic save feature to the resumable activities.
|-
|31 May to 1st June
|Send in patches to be reviewed by community.
|Make necessary changes as per suggestions by the mentor.
|-
|-
|19 May to 31 May
|2nd June to 15th June
|Start developing the “Shared-project” tool.
|Start writing the screenshot popup alert.
* Create a mini-journal instance that will be shared.
* Code a new screenshot popup alert module include text entry, screenshot preview and interactive buttons.
* Design a single mini-journal instance that will handle instances of other shared activities.
* Make adjustments to the activity base class file and to home view to make the module compatible with them.
|-
|-
|1 June to 13 June
|16th June to 17th June
|Implement the File-Syncer System.
|Send in patches for review by the mentor.
|Make necessary modifications to the patches.
|-
|-
|14 June to 24 June
|18th June to 24th June
|
|Discuss the backend working of the feature with mentor.
|Design the layout for the user interface modications.
|Start working on activity resume feature.
|-
|-
|25 June to 26 June
|25th June to 26th June
|Prepare for mid-term evaluation.
|Prepare for midterm evaluation.
|Re-evaluate the submitted patches and update the documentations.
|'Save As' alert and Screenshot alert would be implemented by the midterm evaluation.
|-
|-
|27 June to 28 June
|27th June to 28th June
|'''Midterm Evaluation'''
|'''Midterm Evaluation'''
|-
|-
|29 June to 5 July
|29th June to 5th July
|Buffer Week
|Buffer Week
|-
|-
|6 July to 9 July
|6th July to 15th July
|Analyze the feedback and clean up the code.
|Continue with the work on 'Activity resume' feature.
|Work on the home view to implement one Click and <Alt>Click start/resume facility.
|-
|-
|10 July to 26 July
|16th July to 17th July
|
|
* Add alerts to the file-syncer system that would alert the user for changes in state of shared activity.
* Send in patch for review.
* On completion, send patch for review.
* Test the overall stability of the all the implemented features.
|-
|-
|27 July to 2 August
|18th July to 19th July
| Would like to a day or 2 days off.
|-
|-
|-
|7 August to 10 August
|20 July to 15 July
|Implement the Icon View for Journal.
|Discuss the Sugar backup-restore specifications with the mentor.
* Understand the current backup/restore mechanism as developed by Mr.Martin Langhoff.
* Redesign the resync feature and add user selection based upload to Owncloud repository.
* Code the automatic garbage cleanup to free up space occupied by unnecessary(least frequently used) activities.
* Implement the selection based download feature from the Owncloud repository.
* Modify the read/write access to the online cloud storage in accordance with the implemented features.
|-
|-
|11 August to 17 August
|16 August to 18 August
|
|
* UI improvements.
* UI improvements.
* Improve code efficiency.
* Improve code efficiency.
* Send PRs for review from community members.
* Send patches for more reviews.
|-
|-
|18 August to 22 August
|19 August to 22 August
|
|
* Fix bugs.
* Fix bugs.
* Documentation and Update the wiki page of Journal, describe the new features that are added.
* Document the implemented feature on respective wiki pages and describe the features.
* Add comments that will help further development.
* Add comments that will help further development.
|-
|-
* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
*''' Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant. '''