161
edits
Changes
→Additional Project Ideas For MB
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)
/* Project Ideas -- Experiments and Documentation for Music Blocks and Robotics*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks' First Steps for Robotics <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of Javascript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstratable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots
/* Project Ideas -- Become a Prolific Music Blocks Composer: Create Examples, Compositions, and New Experiments Every Day!*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Create Examples, Compositions, and New Experiments Every Day! <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks program; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (timeframes, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definate plus.
/* Project Ideas -- Music Blocks UI Improvements and Implementation*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks UI Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, Javascript, and HTML. Published work on UI (links to code, websites, etc)
/* Project Ideas -- Scales/Modes/Keys Design Improvements and Implementation*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that a future (or current) developer could read and implement.
/* Project Ideas -- Music Analysis and Visualization Tools*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Create UI features for music analysis and visualization <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; javascript knowledge
/* Project Ideas -- Music Blocks Musical Ornaments Features*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Musical Ornaments Features <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)
/* Project Ideas -- Music Blocks Widget: New Features and Improvements*/
|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Widget Improvements <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)
|}
|}