Atuljangra

User:Atuljangra (edit)

Revision as of 15:04, 29 March 2012

2,223 bytes added , 29 March 2012

→‎Y: Your task

Atuljangra

38

edits

@@ Line 115: / Line 115: @@
 :::	Users will have benefit of faster navigation, better and informative user interface so that it can make their task easy and fast.Improved UI , Improved IRC client will be very 	helpful to the users. This will increase the user experience of GNU Octave.
 ::*GNU Octave:
-	GNU OCtave will itself be benefited as they will get a better product which will be ready for production. This project will  result in a product that will prove that hiding source is not necessary to produce a quality GUI.This will somehow aim to satisfy Matlab users who want to be shielded from the horrors of a CLI interface.
+:::	GNU OCtave will itself be benefited as they will get a better product which will be ready for production. This project will  result in a product that will prove that hiding source is not necessary to produce a quality GUI.This will somehow aim to satisfy Matlab users who want to be shielded from the horrors of a CLI interface.
 ** If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list?
+:I have applied for an idea from the idea's list.
 * Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). Optionally include two or three milestones you expect.''
+:Plan:
+:*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:
+		(Community bonding period)
+.Focus will be on community bonding , know about the mentor personally and discuss things related to the project.
+.Documentation Reading.
+.To do self coding with GNU Octave to improve my further understanding with the Core Octave and GUI.
+.To discuss the methods for making Octave more 	thread-safe.
+.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
+		(Coding Period starts)
+. Improving IRC Client.
+.Making GUI more flexible by improving MainWindow.
+.Improving Documentation Browser.
+.Other small basic Implementations
+:*July 9.
+		Mid-Term Evaluation
+:*July 10-July 31 :
+.Thread safety will be considered and implemented in this time.
+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.
+.Documentation of whole work done.
+:*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:
+		Official Pen Down.
+		Time for Testing  and scrubbing the code.
+:*August 20:
+		Firm Pencil Down.
+:*If you are unable to complete the project, are the results from part-way through still useful? How?
+:	Yes Each and every part is pretty independent, completion of each part 	will be useful for Octave.
+:*How will everybody know whether things are on-track at the halfway evaluation point?
+:	If all the work stated before july 9 is completed, then I will be certainly ahead of halfway of project.But if in any unavoidable circumstances, I am not able to complete the three points before July 9, then half-way will be more than two points covered. And then the buffer time will be used
 <!--[[Category:Summer of Code 2012]]-->