137
edits
Changes
Summer of Code/2016/Nutritional Microworld (view source)
Revision as of 02:30, 25 March 2016
, 02:30, 25 March 2016→About my project
* ''' 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.
'''
'''
{|class="wikitable"
|-
! DAYS !! WORK TO BE DONE
|-
| style="width: 200px;" | May 5 - May 10 || Go through turtleblocksJS code thoroughly to understand the flow, primitives, methods in good detail. I have basic understanding of the code because of my previous contribution to sugar.
|-
| May 11- May 13 || Understanding Western Music Theory deeply(I have basic the knowledge but I believe there’s always room for improvement for everyone), I am good in Indian classical music, so it’ll be easier to understand the analogy between both.
|-
| May 14 - May 16 || Discuss about Features, Functionalities and architecture of the project. Discuss about methods of implementation specified in this proposal.
|-
| May 17 - May 23 || Narrowing down turtleblocksJS, getting rid of stuff we don’t need. Making UI / UX, working on design aspects.
|-
| May 24 - June 4 || -> Making structure for the activity i.e. how blocks, blockfactory etc should work.
-> Making primitive blocks required.
|-
| June 5 - June 15 ||
Making a basic Music tools suite.
Implementing functionalities like:
->Playing note with different note values
->Playing input music files
->Pitch, Time signature
->Chunks for sequencing notes and giving modularity to melodies.
->different type of oscillators
->implementing polyphony by playing multiple chunks together
->recording sound.
->implementing cache for the activity to expedite the process of retrieving data
|-
| June 16 - June 19 || Break for family trip.
|-
| June 20 - June 23 || Adding functionality to create virtual instruments(their sounds) and also required parameters to do the same.
|-
| June 24 - June 26 || Buffer period, Taking reviews from Devin and Walter for the work done so far
|-
| June 27 || Apply for Mid-term evaluation
|-
| June 28 - July 3 || -> Improving UI/UX
-> improving primitives(to run blocks, palettes etc in backend)
-> Documentation of work done so far
-> tracking status of commitments.
-> testing the functionalities implemented so far by covering all the possible cases
|-
| July 4 - July 10 || Begin working on Automation, where user could put the logic(like steps to go up/down, scale, time signature) which could create a notes sequence. Order of chunks could be manipulated using logic sequences.
|-
| July 11 - July 14 || I will continue working on Automation (this functionality could also require some changes in primitives) and complete it in this time period.
|-
| July 15 - July 19 || Implementing export functionality of the project made in the activity (as MIDI, lilypond, XML, .tb) and .tb file could act as input to the turtle Art and I will try to implement that output .tb file of turtle Art project could also act as input file for for music blocks.
|-
| July 20 - July 25 || Buffer period
|-
| July 26 - Aug 1 || Making examples for the activity, which could be imported, it’ll help users to get better understanding of the functionalities out there, and how to use them.
|-
| Aug 2 - Aug 12 || Discuss with Walter and Devin, if there’s anything more that we’d like to implement. Implement it.
|-
| Aug 13 - Aug 16 || -> Organize whole code
-> UI improvements.
-> testing all the modules and variations.
-> fix remaining small issues
|-
| Aug 17 - Aug 20 || > Pencils down date
-> Scrub code
-> re-factor the code to remove out unnecessary/commented code and its repetitions also
-> adding comments which will help further development of the activity easier for other people.
|-
| Aug 21 || -> Firm pencils down date
-> Submit final evaluations to Google.
|}