100
edits
Changes
Jump to navigation
Jump to search
Line 83:
Line 83: − − '''<br> − ''' − {| class="wikitable" − ! style="width: 150px;" | Week − !Task − |- − | − |<br> − |Get thorough with Journal code. Analyze its working. I have basic understanding of the code because of my previous contributions to sugar. − |- − |Till 18 May − <br> − |Analyze more on how collaboration works in sugar. − <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 23 May − <br> − |Begin coding for “Add New Entry” tool. − − Design a Pop-up Box to give title. − <br> − Create a File Dialog/Chooser View of HomeView. − |- − |24 May to 8 June − <br> − |Start developing the “Share Project” tool. − − - Create a mini-journal instance that will be shared. − − - Develop this Mini-Journal instance to handle the instances of other activities for sharing. − |- − |9 June to 24 June − <br> − |.- Test for collaboration of mini-journal. − <br> − - Write test cases that can be furthur used for testing. − <br> − - Send patches of the feature completed and get feedback from community on the features that are implemented. − |- − |25 June to 26 June − |Prepare for mid-term evaluation. − − The major features listed above would be implemented till mid-term. − |- − |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 16 July − |Integrate the Chat activity in mini-journal. − |- − |17 July to 23 July − <br> − |Finish up the small features. − − - Complete the Icon view for Journal. − − - Implement “Sort alphabetically” mainly for the list of files of the mounted devices like USB. − − - Convert Journal Activity to Sugar Service. − |- − |24 July to 7 August − |Discuss with Sam and other community members on the current progress made and get a few more ideas that could be implemented in a short span of time. − − Implement them. − |- − |8 August to 15 August − <br> − |- Improve code efficiency − − - UI improvements − − - Thorough Testing − − - Fix relevant bugs − |- − |16 August to 22 August − <br> − |- Merge the changes to the source code of Journal. − <br> − - Documentation and Update the wiki page of Journal, describe the new features that are added. − <br> − - Add comments that will help further development. − |- − |21 August to 24 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.
Summer of Code/2016/Journal Rethink (view source)
Revision as of 08:06, 20 March 2016
, 08:06, 20 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.'''