Changes

Jump to navigation Jump to search
50 bytes added ,  13:33, 23 January 2018
Line 110: Line 110:     
|-
 
|-
| valign=top width="15%" style="background:#e3e4e5;" |Lilypond Developer Documentation and Methodical Improvements to how Music Blocks generates Lilypond output <br>[[File:Music-Blocks.png|90px|thumb|center]]
+
| valign=top width="15%" style="background:#e3e4e5;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output <br>[[File:Music-Blocks.png|90px|thumb|center]]
 
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
 
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
 
| align=left valign=top |
 
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to 1) document how the Music Blocks source code works for current and future developers to learn and benefit from, 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), and 3) improve existing code where needed and implement needed features.
+
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed; and implement and improve lilypond export features.
+
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
 
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript
 
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript
  

Navigation menu