Sugar Labs - User contributions [en]

Features/Dashboard

2020-04-05T12:42:21Z

HrishiP: Created page with "<noinclude> Category:Feature Page Incomplete . </noinclude> <!-- All fields on this form are required to be accepted. We also request that you maint..."

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]
</noinclude>





== Summary ==
The Dashboard is available as an activity and could be integrated into Sugar desktop's Journal feature. The Dashboard gives the user insight of their activity.

== Owner ==
* Name: [[User:HrishiP| Hrishi Patel]]
* Email: Hrishi Patel <hrishipatel99@gmail.com>

== Current status ==
* Last updated: 30th August 2019
* Percentage of completion: 90%

== Detailed Description ==
* The Dashboard shows the following three things on the top:
** Total Activities Installed: Shows the number of activities the user has installed on their system.
** Number of Journal Entries: Shows the number of Journal entries.
** Total Files: Shows the total number of files present in the Journal.
* Shows recent journal entries in a TreeView, users can sort it to show latest Journal entries, show only files or show the oldest journal entries.
* A pie-chart which shows which activity is used the most.
* A GitHub styled heatmap which shows user's activity throughout the year. On clicking a day, it will show journal entries from that day.

== Benefit to Sugar ==
This feature provides the user to have a better track of their activities when using Sugar. The user can check their activities on a particular day of the year, can see files generated by them and keep a track of their system. The feature can be integrated with Journal.

== Scope ==

''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* Review my pull request and commits for the changes I make.
* documentation changes.
* testing the feature as I make changes.

== How To Test ==
The activity is available here: https://github.com/sugarlabs/Dashboard.activity
The integration PR: https://github.com/sugarlabs/sugar/pull/851

== Dependencies ==

No dependencies.

== Contingency Plan ==

None necessary, revert to previous release behavior.

== Documentation ==

See PR #851 at https://github.com/sugarlabs/sugar/pull/851

== Release Notes ==

Dashboard

Dashboard activity is available. https://github.com/sugarlabs/Dashboard.activity
The integration of Dashboard to Journal is in the works.

== Comments and Discussion ==
* Link to the discussion on lists.sugarlabs.org:
https://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg45977.html,
https://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg46097.html,
https://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg45992.html,
https://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg46013.html,
https://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg46066.html,

* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Features/Variable-Appearance-of-Buddy-Icon

2019-08-30T11:34:18Z

HrishiP: Created page with "<noinclude> Category:Feature Page Incomplete . </noinclude> <!-- All fields on this form are required to be accepted. We also request that you maint..."

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|.]]
</noinclude>





== Summary ==
This feature is a modification to the existing XO icon on the Sugar desktop. The XO icon will now change based on the number of journal entries, battery status, and disk usage.

== Owner ==
* Name: [[User:HrishiP| Hrishi Patel]]
* Email: Hrishi Patel <hrishipatel99@gmail.com>

== Current status ==
* Targeted release: 0.115-0.116
* Last updated: 30th August 2019
* Percentage of completion: 70%

== Detailed Description ==
* The XO icon on the Sugar desktop changes according to:
** Number of Journal entries. If number of journal entries are less than 10, the embryo will be the style. If the number of journal entries is between 10 and 50, Teen style is selected. For more than 50 journal entries, the Adult style will be selected.
** Battery status. Badges are shown if a battery is detected. The badge uses the existing battery icon in the Sugar artwork.
** Disk usage. Currently, the icons will only change for when disk status is below 50%, greater than 50% or greater than 90%. The stroke size of the icons will change accordingly.
* Provides a setting (GSettings) to enable or disable the feature.
In future, the widget will be based on Cairo and will not be using icons for the styles.

== Benefit to Sugar ==
This feature provides a visual update to the existing XO icon on the Sugar desktop. The user will know more about their Journal, their disk and battery status from the Desktop. The idea was to make the XO icon adapt according to the properties state above for better user experience.

== Scope ==

''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

* Review my pull request and commits for the changes I make.
* documentation changes.
* testing the feature as I make changes.

The feature is implemented in buddyicon.py (jarabe/view/buddyicon.py).
The code at extension/deviceicon/battery was also modified.
A gsetting was added to make enabling the feature optional.

==UI Design==

No direct impact on the workflow. The artwork was changed (https://github.com/Hrishi1999/sugar-artwork/tree/tamagotchi-widget).
In future, Cairo will be used to draw the icon instead of using too many icons.

== How To Test ==
Use this branch to test changes: https://github.com/Hrishi1999/sugar/tree/tamagotchi-widget-feature
To test battery badges, the device must be battery-equipped. You will notice a changes to XO icon on Desktop.

== User Experience ==
You will notice that the XO icon on Sugar desktop will change according to the properties state above (journal entries, disk usage, and battery)

== Dependencies ==

No dependencies.

== Contingency Plan ==

None necessary, revert to previous release behavior.

== Documentation ==

See PR #852 at https://github.com/sugarlabs/sugar/pull/852

== Release Notes ==

Variable Appearance of Buddy Icon

This feature is a modification to the existing XO icon on the Sugar desktop. The XO icon will now change based on the number of journal entries, battery status, and disk usage.

== Comments and Discussion ==
* Link to the discussion on lists.sugarlabs.org: http://lists.sugarlabs.org/archive/sugar-devel/2019-July/057072.html,
http://lists.sugarlabs.org/archive/sugar-devel/2019-July/057100.html,
http://lists.sugarlabs.org/archive/sugar-devel/2019-June/057003.html,
http://lists.sugarlabs.org/archive/sugar-devel/2019-May/056832.html

* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]]

Summer of Code/2018

2018-02-01T16:58:40Z

HrishiP: /* Project Ideas */

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/5544862897143808/ Sugar Labs at GSoC]

== Project Ideas ==

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#e3e4e5;" |Migration of wiki activity pages to git
| valign=top width="15%" |Activity team
| align=left valign=top |
;Brief explanation: We have 345 pages under [[Activities]] in this wiki. It would be more sustainable in the long run if these pages were embedded (in Markdown format) in their corresponding git repositories.
;Expected results: Definition of migration process; migration of the majority of these pages
;Knowledge prerequisites: Knowledge of Markdown and Mediawiki markup; experience with git.
|-
| valign=top width="15%" style="background:#f3f4f5;"|GTK-4 exploration
| valign=top width="15%" style="background:#f3f4f5;"|Devel Team
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation: GTK-4 is coming soon [https://mclasen.fedorapeople.org/gtk4-devconf2018.pdf]: probably in 2018. We need to be better prepared for the transition than we were for GTK-3.
;Expected results: Design of a workflow for transitioning from GTK-3 to GTK-4
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;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
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#f3f4f5;"|Full-color icons
| valign=top width="15%" style="background:#f3f4f5;"|Design team
| align=left valign=top style="background:#f3f4f5;"|
;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 [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] 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.

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;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

|-
| valign=top width="15%" style="background:#f3f4f5;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG 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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | Sam CG
| align=left valign=top |
;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 [https://github.com/sugarlabs/aslo-v3].

|-
| valign=top width="15%" style="background:#f3f4f5;"|Lesson Plans for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md 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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Cristian Garcia
Abhijit Patel Ibiam Chihurumnaya

Hrishi Patel
| align=left valign=top |
;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

|-
| valign=top width="15%" style="background:#f3f4f5;"|Updating a new design of Sugarlabs wiki
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Walter bender
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;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

|-
|valign=top width="15%" style="background:#e3e4e5;" |Outreach
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;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]
;Knowledge prerequisites: community outreach experience; some coding experience (to create requisite artifacts)

|-
|valign=top width="15%" style="background:#f3f4f5;"|Making a Beginner Guide
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Walter Bender
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;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? " . [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html 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 )

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Social Sugarlabs website [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" | Jaskirat Singh Samson Goddy
Hrishi Patel
| align=left valign=top |
;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 have user logins, feed and a blog thst can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience

|-
| valign=top width="15%" style="background:#f3f4f5;"|Making a marketing animated website page of sugarlabs
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Samson Goddy
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;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 [http://meta-liquid.com/ See[1] ], [http://education.iceandsky.com/ 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, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| 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 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.
;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

|-
| valign=top width="15%" style="background:#f3f4f5;"|<strike>Migrating Planet Sugar to Medium</strike>
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Samson Goddy
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation:We need to change the look of [http://planet.sugarlabs.org/ Planet Sugar] by embedding [[https://medium.com/|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)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Making Testimonials page on Sugar Labs website
| valign=top width="15%" | Jaskirat Singh Walter Bender
| align=left valign=top |
;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
;Knowledge prerequisites: Make a research about people using Sugar ...get interaction with them ; know about Sugarlabs and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)

|-
| valign=top width="15%" style="background:#f3f4f5;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| 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.

|-
| valign=top width="15%" style="background:#f3f4f5;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;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)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima
| 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.

|-
| valign=top width="15%" style="background:#f3f4f5;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#f3f4f5;"|
;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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| 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)

|-
| valign=top width="15%" style="background:#f3f4f5;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#f3f4f5;"|
;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)

|-
|valign=top width="15%" style="background:#e3e4e5;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské
Hrishi Patel
| align=left valign=top|
;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.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)

|-
|valign=top width="15%" style="background:#f3f4f5;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#f3f4f5;"|Lionel Laské Michaël Ohayon
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]
|}

Google Code In 2017

2017-10-11T17:15:20Z

HrishiP: /* Mentors */

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2017]]</noinclude>

This is the project page for the Sugar Labs application to [https://developers.google.com/open-source/gci/ Google Code In 2017]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the fourth week of October 2017.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

https://developers.google.com/open-source/gci/resources/contest-rules

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

'''Details regarding the required forms and paperwork are here: [[Google Code In 2017/Participate#Students]].'''

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org

== Why Sugar Labs is participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs and Sugar development ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2017/background}}

== This is a stub for 25+ example tasks new for GCI 2017. ==

Note, more detailed task descriptions will be available once the contest begins.

=== beginner tasks ===
# Install the Sugar development environment by following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html].
# Install Sugar in a virtual machine.
# Install Sugar packages on Ubuntu, Debian, or Fedora.
# Create an example program in Turtle Blocks (See [https://www.pinterest.com/walterbender/turtle-art/] for some ideas).
# Create an example program in Music Blocks.
# Create a simple machine in Physics.

=== general tasks ===
# Investigate Google Fuzzing tool (Research)
# Music Blocks examples (Documentation/Training)
# Bugzilla clean up (QA)
# Teach me how to draw activity (Code: Javascript)
# Plugin manager for Turtle JS (Code: Javascript)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# Improvements to Lilypond interface (Code: Javascript)
# Add more synths/sound fonts to Music Blocks (Research)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Refactor Planet server for Turtle Blocks (Code: Python)
# Wiki cleanup (Documentation)
# Write a Turtle plugin (Code: Javascript)
# Write a Pinetrest plugin for the Sugar Journal (Code: Python)
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (Code: Javascript)
# Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
# Create a 60 second promotional video on Sugar and its community (Outreach)
# Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
# DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach)
# Gather information on who could benefit from using or knowing about Sugar. (Research)
# Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
# Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach)
# Write a review about an Activity in Sugar. (Documentation)
# Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Outreach)
# Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
# How should the Sugar UI change to accommodate a small screen? (User interface)
# What else should be made easier to customize in Sugar with minimal programming? (User interface)
# Create a unit tests for a JavaScript activity (Quality assurance)
# Write a JavaScript version of [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] (Code: JavaScript)
# Design the music equivalent of Turtle Confusion for Music Blocks (Research)
# Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
# Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript)
# Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript)
# Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)

Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.

Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].

== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2017/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - co-administrator
* Ignacio Rodriguez -co-administrator
* Hrishi Patel

Talk:Raspbian

2017-06-21T05:29:13Z

HrishiP:

Testing on a RPi3 with a fresh install of Jessie. Installed sucrose and /usr/share/xsession/sugar.desktop looks fine, but not option to select Sugar Desktop when I try to login (no option of any sort). --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 08:33, 31 December 2016 (EST)

Found a panel for manually setting the desktop session. After logging out and logging back in, I got the color selector, gender selector, and a broken grade selector. Then everything switched back to the default desktop manager, but the Sugar cursor remained loaded :) Sugar is somewhere on the machine; but getting to it remains a challenge. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 12:01, 31 December 2016 (EST)

Tried running Turtle Art from the shell and from the Education menu: Seg Fault. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 08:33, 31 December 2016 (EST)

Started from scratch and got some unmet dependencies when trying to 'sudo apt install sucrose':
pi@raspberrypi:~ $ sudo apt install sucrose
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
sonic-pi : Depends: libQt5printsupport5 but it is not installable
sucrose : Depends: sugar-session
Depends: python-carquinyol
Depends: sugar-chat-activity
Depends: sugar-browse-activity
Depends: sugar-read-activity but it is not going to be installed
Depends: sugar-log-activity
Depends: sugar-write-activity but it is not going to be installed
Depends: sugar-terminal-activity but it is not going to be installed
Depends: sugar-pippy-activity but it is not going to be installed
Depends: sugar-imageviewer-activity but it is not going to be installed
Depends: sugar-jukebox-activity but it is not going to be installed
Recommends: olpc-powerd but it is not going to be installed
Recommends: ipython but it is not going to be installed
Recommends: python-elements but it is not going to be installed
Recommends: csound but it is not going to be installed
Recommends: gstreamer1.0-plugins-bad but it is not going to be installed
Recommends: gstreamer1.0-plugins-ugly but it is not going to be installed
Recommends: python-sugar-toolkit
Recommends: python-sugar
Recommends: gtk2-engines-sugar (>= 0.110)
Recommends: sugar-calculate-activity but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Ran:
sudo apt-get -f install
sudo apt install sucrose

Then:
echo sugar >> .xsession

Logged out and back in and Sugar is running.

Turtle works; Browse fails due to no module collabwrapper.

But it is a start :) --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 17:40, 31 December 2016 (EST)

:Thanks for testing. It is a moving target; I didn't get what you saw. Retested today;

:*Browse fail to start is [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848840 848840] caused by missing file when [https://anonscm.debian.org/cgit/pkg-sugar/sugar-browse-activity.git/commit/?id=88ea788b80155b3f0e065cced0e5599f6c59158b Jonas added] collabwrapper. A new release of Browse might help.

:*Physics fails to start, box2d_arm7 not present.

:*Write shows black screen. Since fixed in [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842443 842443] and abiword 3.0.2-2 arrived in Raspbian, exposing the flicker problem, see [https://bugs.sugarlabs.org/ticket/4915 #4915].

:*Jukebox fails to start; the `import player` invokes the Python Image Library instead. Tracked at [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554906 554906] and I've since *avoided* the problem in [https://github.com/sugarlabs/jukebox-activity/commit/c913a7b0803c25febc6787e63e7392bd52ca2094 c913a7b].

:The cursor change is Sugar changing the settings for the user instead of maintaining separate settings for the user and Sugar combined. I've prototyped a fix with a split-brained GSettings backend.

:These are all problems common to Debian, Ubuntu and Raspbian. Nothing specific to Raspbian or Raspberry Pi hardware. So if we can fix these problems in Debian they will be fixed consequently in Raspbian. --[[User:Quozl|Quozl]] ([[User talk:Quozl|talk]]) 23:22, 31 March 2017 (EDT)

== testing with rdesktop (may not be relevant) ==

(Using 640x480)
# thumb drives are not shown in the journal, however you can see them using "df -h"
# cursor shows as white with a black background
# terminal "help" button is not working (may not be raspbian related, but just found it)
# When clicking view details in a journal entry (the right arrow) it shows nothing
# Right click in the journal sometimes works and sometimes doesn't

[http://people.sugarlabs.org/ignacio/raspbian/03_01_2017/ Here are the logs]
-- [[User:Ignacio|Ignacio]] ([[User talk:Ignacio|talk]]) 13:53, 3 January 2017 (EST)

:Same things with rdesktop happen on Ubuntu and Debian, so it isn't a Raspbian thing. USB drives won't be shown because the rdesktop user is not in the local "seat" with authority. Cursor is some sort of problem with rdesktop. Journal problems are part of 0.110 and have been fixed since in git. --[[User:Quozl|Quozl]] ([[User talk:Quozl|talk]]) 23:12, 31 March 2017 (EDT)

== Sugar on RPI image ==

This image can be considered still in beta. This is not the final build.

Here is the link : [https://drive.google.com/file/d/0B1YK6wpv2W0eQUJrRldiVU1fczQ/view Download]

Repository : [https://github.com/drtyhlpr/rpi23-gen-image here]

Fork used: [https://github.com/hrishi1999/rpi23-gen-image here]

If the image does not work on the first boot (or fails to login), please restart your RPI and try again.
--[[User:HrishiP|HrishiP]] ([[User talk:HrishiP|talk]]) 10:49, 21 June 2017 (IST)

Summer of Code/2017

2017-05-19T15:03:09Z

HrishiP: /* Project Ideas */

== Project Ideas ==

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;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
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks [[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues 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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez Samson Goddy Tymon Radzik
Hrishi Patel
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | Tony Anderson
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugdash}}Sugarizer Server Dashboard [[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugmdm}}Sugarizer Deployement and Management Tool for Android [[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
Hrishi Patel
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Sam Parkinson
Abhijit Patel
| align=left valign=top |
;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 Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators. See https://wiki.debian.org/SugarBlend and [[Debian]].
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
Hrishi Patel
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: An image for RPi, which boots to a Sugar desktop environment, and is suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink 
| valign=top width="15%" | Abhijit Patel Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}|}|}|}

Summer of Code/2017

2017-03-21T13:32:30Z

HrishiP: /* Project Ideas */

== Project Ideas ==

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;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
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks [[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues 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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez Samson Goddy Tymon Radzik
Hrishi Patel
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | (volunteers?)
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugdash}}Sugarizer Server Dashboard [[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugmdm}}Sugarizer Deployement and Management Tool for Android [[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Sam Parkinson
Abhijit Patel
| align=left valign=top |
;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 Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators.
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
Hrishi Patel
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: Packaged Sugar for RPi suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink 
| valign=top width="15%" | Abhijit Patel Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}|}