| 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
|
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
|
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 Music Blocks issues.
- 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
|
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)
|
New Social Sugarlabs website
|
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
|
| 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
|
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
|
