User:CodingCoffee: Difference between revisions

Jump to navigation Jump to search
Line 103: Line 103:
* 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"). If possible, include two or three milestones you expect.''
* 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"). If possible, include two or three milestones you expect.''
** I plan to work 35 hours a week. This is the schedule I would like to follow:
** I plan to work 35 hours a week. This is the schedule I would like to follow:
'''Before 30 May:'''
** '''Before 30 May:'''
I'll try to be more familiarized with the community and the mentors, while discussing and defining my problem statement for all my 3 areas of interest.
*** I'll try to be more familiarized with the community and the mentors (using mailing list, IRC Channel), while discussing and defining my problem statement for all my 3 areas of interest.
'''Phase 1, until 30 June:'''
*** Also I'll try contributing to short projects, thereby understanding the process of submitting a commit to an open source project.
- Study the current implementation of Octave kernel for Jupyter.
** '''Phase 1, until 30 June:'''
- Study various searching algorithms, including the one implemented in the Ubuntu terminal for suggesting the commands.
*** Study the current implementation of Octave kernel for Jupyter.
- Familiarize myself with the MediaWiki[https://www.mediawiki.org/wiki/MediaWiki] for Octave Code sharing
*** Study various searching algorithms (including the one implemented in the Ubuntu terminal for suggesting the commands in case there is a spelling error made by the user)
 
*** Tackle the following issues:
'''Phase 2, until 28 July:'''
**** provide one or more suggested corrections to the user when a command line entry produces an error
- Implement the problem statement: 'provide one or more suggested corrections to the user when a command line entry produces an error'
**** recognition and suggested correction for apparent syntax errors
- Come up with solutions for the grey/gray problem[https://savannah.gnu.org/bugs/?46881]
**** function suggestion(s) when a 'close' match is found
 
** '''Phase 2, until 28 July:'''
'''Phase 3, until 29 August:'''
*** Tackle the following issues:
 
**** Come up with solutions for the grey/gray problem[https://savannah.gnu.org/bugs/?46881]
**** multiple suggestions if more than one option seems likely, along with a user-friendly method of selecting the appropriate choice
**** user selectable option to disable and/or customize the suggestion behavior
**** correct operation, or graceful degradation, whether Octave is run in GUI or command-line mode
*** Get accustomed to libcurl and MediaWiki
*** Familiarize myself with the MediaWiki[https://www.mediawiki.org/wiki/MediaWiki] for Octave Code sharing
** '''Phase 3, until 29 August:'''
*** Buffer zone, in case any of the previous commitments are not executed as scheduled
*** Implement Octave code sharing




[[Category: Summer of Code]]
[[Category: Summer of Code]]
23

edits

Navigation menu