Changes

Jump to: navigation, search

Summer of Code/2018

672 bytes added, 14:44, 29 January 2018
Project Ideas
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Internationalization and Localization| valign=top width="15%" style="background:#d7d8d9;" |Chris Leonard| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Music Blocks optimizations<br>[[File:Music-Blocks.png|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Maintenance of activities.sugarlabs.org (ASLO)| valign=top width="15%" style="background:#d7d8d9;" | Sam CG| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. During GSoC 2017 we built ASLO v3 to address a number of deficiencies. But we have a few odds and ends that need to be addressed to bring the new site on line.
;Expected results: Update missing license and repository info on the activities found in the Sugar Labs github repository. Popular the database for the new ASLO. Do extensive testing (including creating some test suites.) Document future maintenance on the Wiki.
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Just say no to GTK2| valign=top width="15%" style="background:#d7d8d9;" | Ignacio Rodriguez<br>Cristian Garcia
Abhijit Patel<br>Ibiam Chihurumnaya
| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
|-
|valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Outreach| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: We don't have a very friendly approach to outreach to new contributors. It would be great to make it easier to get involved and to navigate the path towards contributing to Sugar Labs. The goal of this project is to revamp our approach to outreach.
;Expected results: A set of pages similar to [https://publiclab.github.io/community-toolbox/] and [https://publiclab.org/wiki/software-outreach]
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |New Social Sugarlabs website<br>[[File:Social Site.jpg|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Jaskirat Singh<br>Samson Goddy| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation: Its a social website that can be used to attract maximum users and everything ( Blogs, New projects, Softwares, Activities, etc) can be uploaded on it which will attract more user and create their interest
;Expected results: It should be over viewed by people around the world
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output <br>[[File:Music-Blocks.png|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser| align=left valign=top style="background:#d7d8d9;"|
;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: 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.
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Making Testimonials page on Sugar Labs website| valign=top width="15%" style="background:#d7d8d9;" | Jaskirat Singh<br>Walter Bender| align=left valign=top style="background:#d7d8d9;"|
;Brief explanation:Well, Develop a testimonal webpage on Sugarlabs website by making a good research about the users who have experienced the world of Sugar. That should include videos, blog posts and many more things. For such type of layout example visit ( https://www.chownow.com/testimonials-reviews ) and ( https://www.codecademy.com/stories )
;Expected results: A good layout with more views about sugar Users
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Create Examples, Compositions, and New Experiments Every Day! <br>[[File:Music-Blocks.png|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima| align=left valign=top style="background:#d7d8d9;"|
;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
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser<br>Sachiko Nakajima| align=left valign=top style="background:#d7d8d9;"|
;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.
|-
| 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<br>Sachiko Nakajima
| 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.
|-
| valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Music Blocks Musical Ornaments Features <br>[[File:Music-Blocks.png|90px|thumb|center]]| valign=top width="15%" style="background:#d7d8d9;" | Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima<br>Marnen Laibow-Koser| align=left valign=top style="background:#d7d8d9;"|
;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)
|-
|valign=top width="15%" style="background:#e3e4e5d7d8d9;" |Sugarizer School Box<br>[[File:Sugarizerschoolbox.jpg|90px|thumb|center]]|valign=top width="15%" style="background:#d7d8d9;" |Michaël Ohayon
Lionel Laské
| style="background:#d7d8d9;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.

Navigation menu