100
edits
Changes
Jump to navigation
Jump to search
Line 94:
Line 94: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Summer of Code/2016/Journal Rethink (view source)
Revision as of 04:19, 22 March 2016
, 04:19, 22 March 2016no edit summary
'''What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then'''
'''What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then'''
'''<br>
<br>
'''
{|
|Days
|Tasks
|-
|31 April to 9 May
|Get thorough with Journal code. Analyze its working. I have basic understanding of the code because of my previous contributions to sugar.
<br>
- Get a better grip over telepathy salut and gabble.
|-
|10May to 18 May
<br>
|<nowiki>- Analyze more on how collaboration works in sugar.</nowiki>
<br>
- 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.
|-
|19 May to 31 May
<br>
|Start developing the “Shared-project” tool.
<br>
- Create a mini-journal instance that will be shared.
<br>
- Design a single mini-journal instance that will handle instances of other shared activities.
|-
|1 June to 13 June
<br>
|Implement the File-Syncer System.
<br>
- Make this system sync the files when the user does not have the activity running.
|-
|14 June to 24 June
<br>
|<nowiki>- Test the working of mini-journal system that is in sync with the File-Syncer system.</nowiki>
<br>
- Write test cases that can be further used for developing and testing.
|-
|25 June to 26 June
|Prepare for mid-term evaluation.
- Send patches of the feature completed for review.
The main Shared mini-journal would be implemented till midterm.
|-
|27 June to 28 June
|Midterm Evaluation
|-
|29 June to 5 July
|Buffer Week
|-
|6 July to 9 July
|Analyze the feedback and clean up the code.
|-
|10 July to 26 July
|<nowiki>- Add alerts to the file-syncer system that would alert the user for changes in state of shared activity.</nowiki>
<br>
- On completion, send patch for review.
|-
|27 July to 2 August
<br>
|Integrate the Chat Activity in mini-journal.
|-
|3 August to 6 August
|Implement the “Add new Item” tool.
- Design the File-Chooser Dialog View for Home View.
|-
|7 August to 10 August
<br>
|<nowiki>- Implement the Icon View for Journal.</nowiki>
|-
|11 August to 17 August
<br>
|<nowiki>- UI improvements.</nowiki>
- Improve code efficiency.
- Test again all the tools and features.
- Send patches for more reviews.
|-
|18 August to 22 August
|<nowiki>- Fix bugs.</nowiki>
<br>
- Documentation and Update the wiki page of Journal, describe the new features that are added.
<br>
- Add comments that will help further development.
|-
|23 August
|Final Evaluation
|}
'''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.'''<br>
'''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.'''<br>