38
edits
Atuljangra
Joined 27 March 2012
→Y: Your task
Atuljangra (talk | contribs) |
Atuljangra (talk | contribs) |
||
| Line 90: | Line 90: | ||
* Did you select a task from our list of proposals and ideas? | * Did you select a task from our list of proposals and ideas? | ||
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ||
Wiki link [http://octave.org/wiki/index.php?title=GSoC_Project_Ideas Ideas Page] | :Yes,I did | ||
:Wiki link : [http://octave.org/wiki/index.php?title=GSoC_Project_Ideas Ideas Page] | |||
:Octave is currently written in C++/QT. Though it have a great UI , but as pointed out by the organisation , it is not ready for production. | :Octave is currently written in C++/QT. Though it have a great UI , but as pointed out by the organisation , it is not ready for production. | ||
| Line 121: | Line 122: | ||
:Plan: | :Plan: | ||
:*Before April 23: | :*Before April 23: | ||
:(Familiarisation period). | |||
:I will familiarise myself with whole , code , try to fix and provide patches for the same. | |||
:*April 23 - May 21: | :*April 23 - May 21: | ||
: (Community bonding period) | |||
: 1.Focus will be on community bonding , know about the mentor personally and discuss things related to the project. | |||
: 2.Documentation Reading. | |||
: 3.To do self coding with GNU Octave to improve my further understanding with the Core Octave and GUI. | |||
: 4.To discuss the methods for making Octave more thread-safe. | |||
: 5.During this period I will remain in constant touch with my mentor and the GNU Octave community. I will remain active on IRC and Mailing lists to discuss and finalize on the modifications (if any) that needs to be on existing strategies and design of new strategies. | |||
:*May 21 - July 8 | :*May 21 - July 8 | ||
: (Coding Period starts) | |||
: 1. Improving IRC Client. | |||
: 2.Making GUI more flexible by improving MainWindow. | |||
: 3.Improving Documentation Browser. | |||
: 4.Other small basic Implementations | |||
:*July 9. | :*July 9. | ||
: Mid-Term Evaluation | |||
:*July 10-July 31 : | :*July 10-July 31 : | ||
: 1.Thread safety will be considered and implemented in this time. | |||
: 2 Any other implementation which can come into consideration later either by me or by my mentor or anybody(User or other Developers) will be implemented in this period. | |||
: 3.Documentation of whole work done. | |||
:*July 31-August 13: | :*July 31-August 13: | ||
: Buffer time kept for unexceptional delays. ( And in case of no delays, we can think of more functionalities to implement or solve bugs) | |||
:*August 13: | :*August 13: | ||
: Official Pen Down. | |||
: Time for Testing and scrubbing the code. | |||
:*August 20: | :*August 20: | ||
: Firm Pencil Down. | |||
:*If you are unable to complete the project, are the results from part-way through still useful? How? | :*If you are unable to complete the project, are the results from part-way through still useful? How? | ||