Summer of Code/2018

From Sugar Labs
Jump to navigation Jump to search

Sugar Labs at GSoC

Project Ideas

Title Mentor Project
Internationalization and Localization Chris Leonard
Brief explanation
A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See Translation Proposal To Do List for details. See Translation Team for framework description.
Expected results
Work flow improvements for i18n
Knowledge prerequisites
Some knowledge of Pootle; some scripting experience; Python and JavaScript
Full-color icons Design team
Brief explanation
We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [1] as one example of how we might proceed.)
Expected results
A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing
Knowledge prerequisites
Knowledge of GTK; Python.
Music Blocks optimizations
Music-Blocks.png
Walter Bender
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.
Knowledge prerequisites
Knowledge of JavaScript, unit testing
Going Beyond Equal Temperament in Music Blocks
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
Most modern music systems are designed around equal temperament. But there are many ways to chose and tune notes in a musical system that offer different expressive characteristics. See also MB issues for temperament, Articles about temperament, scales, and tuning and various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)
Expected results
Extend Music Blocks such that different approaches to temperament are available to the user.
Knowledge prerequisites
Knowledge of JavaScript, music theory
Maintenance of activities.sugarlabs.org (ASLO) Sam CG
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.
Knowledge prerequisites
PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [2].
Lesson Plans for Music Blocks
Music-Blocks.png
Walter Bender
Devin Ulibarri

Hrishi Patel

Brief explanation
We have a Guide, but we really need some more scaffolding in the form of lesson plans.
Expected results
A website and PDF document that can be bound.
Knowledge prerequisites
Knowledge of music theory, writing skills
Just say no to GTK2 Ignacio Rodriguez
Cristian Garcia

Abhijit Patel
Ibiam Chihurumnaya

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.
Knowledge prerequisites
Knowledge of GTK, GST, and Python
Updating a new design of Sugarlabs wiki Jaskirat Singh
Walter bender
Brief explanation
we are lacking in look of wiki.sugarlabs.org page. It looks ugly and unfriendly and need to be updated with a good design
Expected results
New design of Wiki page of Sugarlabs
Knowledge prerequisites
Knowledge of mediawiki and use of some basic languages
Outreach Walter Bender
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 [3] and [4]
Knowledge prerequisites
community outreach experience; some coding experience (to create requisite artifacts)
Making a Beginner Guide Jaskirat Singh
Walter Bender
Brief explanation
We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . Example The goal of this project is to Help newcomers to get introduce in easy way to the world of Sugar Labs
Expected results
A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily
Knowledge prerequisites
community research , GitHub , coding experience ( HTML, CSS )
New Social Sugarlabs website
Social Site.jpg
Jaskirat Singh
Samson Goddy
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
Knowledge prerequisites
Good Layout designing and coding experience
Making a marketing animated website page of sugarlabs Jaskirat Singh
Samson Goddy
Brief explanation
We need to develop a link that is website-page that will include a page with animations explaining all the things we have in Sugarlabs (as a marketing) like these examples See[1 ], See [2 ]
Expected results
A UI/UX layout and a main page that can be used to market the things in an animated way
Knowledge prerequisites
Knowledge of marketing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP, Ruby)
Lilypond Developer Documentation and Methodical Improvements to how Music Blocks generates Lilypond output
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
Music Blocks is capable of exporting Lilypond code of which general instructions can be found here in the Music Blocks guide and its 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". 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.
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.
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


Migrating Planet Sugar to Medium Jaskirat Singh
Samson Goddy
Brief explanation
We need to change the look of Planet Sugar by embedding Medium ( a blogger )into it by using Medium API but design should be changed> Better and interactive layout
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)

/* Project Ideas -- Experiments and Documentation for Music Blocks and Robotics*/

Music Blocks' First Steps for Robotics
Music-Blocks.png
Walter Bender
Devin Ulibarri
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!*/

Create Examples, Compositions, and New Experiments Every Day!
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
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*/

Music Blocks UI Improvements and Implementation
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
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*/

Scales/Modes/Keys Design Improvements and Implementation
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
There are features in 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 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*/

Create UI features for music analysis and visualization
Music-Blocks.png
Walter Bender
Devin Ulibarri
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*/

Music Blocks Musical Ornaments Features
Music-Blocks.png
Walter Bender
Devin Ulibarri
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 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*/

Music Blocks Widget Improvements
Music-Blocks.png
Walter Bender
Devin Ulibarri
Brief explanation
Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see 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 (see issues), and 3) document and fully integrate these new features and improve existing features. 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)