193
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + − + − + + + + + + + + + Line 58:
Line 67: − + Line 98:
Line 107: − + Line 131:
Line 140: − + Line 139:
Line 148: − + Line 147:
Line 156: − + Line 242:
Line 251: + +
no edit summary
== Selected Projects for summer 2018 ==
== Selected Projects for summer 2018 ==
;Rahul Bothra: Port Sucrose from Python 2 to Python 3 ([http://www.pro-panda.tech/2018/05/24/GSoC-First-Post.html blog])
;Rahul Bothra | Pro-Panda: Port Sucrose from Python 2 to Python 3 ([http://www.pro-panda.tech blog])
;Riya Lohia: Going Beyond Equal Temperament in Music Blocks ([https://medium.com/gsoc18-with-sugar-labs blog])
;Ritwik Abhishek: Music Blocks Widget Improvement ([https://musicblocks18.wordpress.com/ blog])
;Ritwik Abhishek: Music Blocks Widget Improvement ([https://musicblocks18.wordpress.com/ blog])
;Vaibhav Aren: Interactive Exercises for Turtle Blocks ([https://vaibhavdaren.wordpress.com/ blog])
;Vaibhav Aren: Interactive Exercises for Turtle Blocks ([https://vaibhavdaren.wordpress.com/ blog])
;Aman Sharma: Sugarizer School Box ([https://amansharmablogblog.wordpress.com/2018/04/26/introduction-to-the-community/ blog])
;Aman Sharma: Sugarizer School Box ([https://amansharmablogblog.wordpress.com/2018/04/26/introduction-to-the-community/ blog])
;Vipul Gupta: Activity Migration ([https://mixstersite.wordpress.com/ blog])
;Vipul Gupta: Activity Migration ([https://mixstersite.wordpress.com/gsoc2018/ blog])
;Anmol Mishra: Port to Python 3 ([https://medium.com/anmolmishra-jiit blog])
;Anmol Mishra: Port to Python 3 ([https://medium.com/anmolmishra-jiit blog])
;Iqra Muhammad: Sugarizer Primero ([https://iqragsoc.wordpress.com/ blog])
;Iqra Muhammad: Sugarizer Primero ([https://iqragsoc.wordpress.com/ blog])
;Mankirat Singh: Sugarizer Exerciser Activity ([https://mankiratsinghtech.wordpress.com/2018/04/27/google-summer-of-code-2018/ blog])
;Mankirat Singh: Sugarizer Exerciser Activity ([https://mankiratsinghtech.wordpress.com/2018/04/27/google-summer-of-code-2018/ blog])
;Rudra Sadhu: Migration of Activity wiki-pages to Git ([https://rdrsadhu.github.io/blog/gsoc2018/ blog])
;Rudra Sadhu: [https://wiki.sugarlabs.org/go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git Migration of activity wiki-pages to GitHub (and simultaneously help-activity)] ([https://rdrsadhu.github.io/blog/gsoc2018/ blog])
;Yash Aragwal:Just say no to GTK+ 2 ([https://medium.com/@yashagrawal3/gsoc-18-with-sugar-labs-2d9bc733cf59 blog])
;Pratul Kumar:Beginner's Guide ([https://medium.com/@pratulkumar/gsoc-introduction-to-the-community-ed47e04e3051 blog])
[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]
[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]
=== Meetings ===
We meet as a group in IRC every Friday at 22IST, 12:30ET, 16:30UTC. The meetings are logged at http://meeting.sugarlabs.org/sugar-meeting/meetings
----
== Project Ideas ==
== Project Ideas ==
|-
|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team<br> Jaskirat Singh<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"|Design team<br> Jaskirat Singh<br>Peace Ojemeh
| align=left valign=top style="background:#fcfcfc;"|
| align=left valign=top style="background:#fcfcfc;"|
;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.). Like if an activity has not closed yet so it will be shown through a badge appearing on an icon. Repo can be found here https://github.com/sugarlabs/sugar-toolkit-gtk3/tree/master/src/sugar3
;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.). Like if an activity has not closed yet so it will be shown through a badge appearing on an icon. Repo can be found here https://github.com/sugarlabs/sugar-toolkit-gtk3/tree/master/src/sugar3
|-
|-
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social<br>[[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social<br>[[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh<br>Samson Goddy<br>Hrishi Patel<br>Shivang Shekhar<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh<br>Samson Goddy<br>Hrishi Patel<br>Shivang Shekhar<br>Peace Ojemeh
Abdulazeez Abdulazeez
Abdulazeez Abdulazeez
| align=left valign=top style="background:#fcfcfc;"|
| align=left valign=top style="background:#fcfcfc;"|
|-
|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Hrishi Patel<br> Jaskirat Singh<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Hrishi Patel<br> Jaskirat Singh<br>Peace Ojemeh
| align=left valign=top style="background:#fcfcfc;"|
| align=left valign=top style="background:#fcfcfc;"|
;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.
;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.
|-
|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser<br>Sachiko Nakajima<br>perriefidelis<br>Jaskirat Singh
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser<br>Sachiko Nakajima<br>Peace Ojemeh<br>Jaskirat Singh
| align=left valign=top |
| 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?
;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?
|-
|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima<br>Peace Ojemeh
| align=left valign=top style="background:#fcfcfc;"|
| align=left valign=top style="background:#fcfcfc;"|
;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.
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
| valign="top" width="15%" style="background:#f7effc;" | Caryl Bigenho
| valign="top" width="15%" style="background:#f7effc;" | Caryl Bigenho
Samson Goddy
Samson Goddy
Peace Ojemeh
| align="left" valign="top" style="background:#f7effc;" |
| align="left" valign="top" style="background:#f7effc;" |
;Brief explanation: Sugarizer is a large collection of many Activities suitable for general audiences on many devices. The goal of this project is to package a subset of the Sugarizer Activities (Maximum of 5) for children 4-7 (grades Pre-K-2) with a young child-friendly UI/UX experience suitable devices. Many of the graphics in the interfaces will be re-designed to accommodate non-readers and very young children who are still developing their fine motor skills. One new Activity for intuitive math concepts will also be developed similar to [https://en.wikipedia.org/wiki/Cuisenaire_rods Cuisenaire Rods]. Sugarizer1° will be non-language dependent so translations will not be needed.
;Brief explanation: Sugarizer is a large collection of many Activities suitable for general audiences on many devices. The goal of this project is to package a subset of the Sugarizer Activities (Maximum of 5) for children 4-7 (grades Pre-K-2) with a young child-friendly UI/UX experience suitable devices. Many of the graphics in the interfaces will be re-designed to accommodate non-readers and very young children who are still developing their fine motor skills. One new Activity for intuitive math concepts will also be developed similar to [https://en.wikipedia.org/wiki/Cuisenaire_rods Cuisenaire Rods]. Sugarizer1° will be non-language dependent so translations will not be needed.