Changes

Summer of Code/2018 (view source)

Revision as of 06:41, 18 February 2018

2 bytes removed , 06:41, 18 February 2018

→‎Project Ideas

Line 7: Line 7:

GSoC projects must involve some coding. Non-coding projects have been removed and saved into [[/Archive]].

−

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #~~e3e4e5~~;"

+

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"

−

|-style="background:#~~787878~~; color: white;"

+

|-style="background:#7409bc; color: white;"

!Title

!Mentor

!Project

|-

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Python 3 port

+

| valign=top width="15%" style="background:#fcfcfc;"|Python 3 port

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Devel Team

+

| valign=top width="15%" style="background:#fcfcfc;"|Devel Team

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;Brief explanation: Python 3 has been here for quite some time. We've investigated how to migrate and now it is time to do it.

;Expected results: A Python 3 version of the Sugar toolkit, as well as the Sugar Desktop and a few activities.

Line 21: Line 21:

|-

−

| valign=top width="15%" style="background:#~~e3e4e5~~;" |Migration of wiki activity pages to git

+

| valign=top width="15%" style="background:#f7effc;" |Migration of wiki activity pages to git

| valign=top width="15%" |Activity team

| align=left valign=top |

Line 29: Line 29:

|-

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|GTK-4 exploration

+

| valign=top width="15%" style="background:#fcfcfc;"|GTK-4 exploration

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Devel Team

+

| valign=top width="15%" style="background:#fcfcfc;"|Devel Team

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;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

Line 37: Line 37:

|-

−

| valign=top width="15%" style="background:#~~e3e4e5~~;" |Internationalization and Localization

+

| valign=top width="15%" style="background:#f7effc;" |Internationalization and Localization

| valign=top width="15%" |Chris Leonard

Shivang Shekhar

Line 46: Line 46:

|-

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Full-color icons

+

| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Design team Jaskirat Singh perriefidelis

+

| valign=top width="15%" style="background:#fcfcfc;"|Design team Jaskirat Singh perriefidelis

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| 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.)

;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing

Line 54: Line 54:

|-

−

+

| valign=top width="15%" | Walter Bender

| align=left valign=top |

Line 62: Line 62:

|-

−

+

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser

+

| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;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.

Line 70: Line 70:

|-

−

| valign=top width="15%" style="background:#~~e3e4e5~~;" |Maintenance of activities.sugarlabs.org (ASLO)

+

| valign=top width="15%" style="background:#f7effc;" |Maintenance of activities.sugarlabs.org (ASLO)

| valign=top width="15%" | Sam CG

| align=left valign=top |

Line 78: Line 78:

|-

−

| valign=top width="15%" style="background:#~~e3e4e5~~;" |Just say no to GTK2

+

| valign=top width="15%" style="background:#f7effc;" |Just say no to GTK2

| valign=top width="15%" | Ignacio Rodriguez Cristian Garcia Abhijit Patel Ibiam Chihurumnaya Hrishi Patel

| align=left valign=top |

Line 86: Line 86:

|-

−

|valign=top width="15%" style="background:#~~f3f4f5~~;"|Making a Beginner Guide

+

|valign=top width="15%" style="background:#fcfcfc;"|Making a Beginner Guide

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Jaskirat Singh Walter Bender Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy

+

| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh Walter Bender Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;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? " . An example is the Coala [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Newcomers' Guide] which is built from [https://github.com/coala/coala/blob/6dae06082017587a260189a787db9cfdc84a148b/docs/Developers/Newcomers_Guide.rst markdown source]. The goal of this task is to Help newcomers to get introduce in easy way to the world of Sugar Labs also make a dasboard for the users so they can get about developed and developing areas. Their contribution can be seen also their presence can be seen with the community.

;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

Line 94: Line 94:

|-

−

+

| valign=top width="15%" | Jaskirat Singh Samson Goddy Hrishi Patel Shivang Shekhar perriefidelis

| align=left valign=top |

Line 103: Line 103:

|-

−

+

| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser

| align=left valign=top |

Line 112: Line 112:

|-

−

+

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney

+

| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;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!!!)

Line 120: Line 120:

|-

−

+

| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima

| align=left valign=top |

Line 128: Line 128:

|-

−

+

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Walter Bender Devin Ulibarri perriefidelis

+

| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri perriefidelis

Hrishi Patel Jaskirat Singh

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| 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.

;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).

Line 137: Line 137:

|-

−

+

| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima perriefidelis

| align=left valign=top |

Line 145: Line 145:

|-

−

+

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis

+

| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| 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.

;Expected results: New Features.

Line 153: Line 153:

|-

−

+

| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser

| align=left valign=top |

Line 161: Line 161:

|-

−

+

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser

+

| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;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.

Line 169: Line 169:

|-

−

+

|valign=top width="15%" |Michaël Ohayon Lionel Laské Hrishi Patel Rishabh Thaney

Shivang Shekhar

Line 183: Line 183:

|-

−

+

−

|valign=top width="15%" style="background:#~~f3f4f5~~;"|Lionel Laské Michaël Ohayon

+

|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské Michaël Ohayon

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;Brief explanation

:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.

Line 198: Line 198:

|-

−

+

−

| valign=top width="15%" style="background:#~~e3e4e5;~~"| Walter Bender Devin Ulibarri Sachiko Nakajima

+

| valign=top width="15%" style="background:#f7effc"| Walter Bender Devin Ulibarri Sachiko Nakajima

−

| align=left valign=top style="background:#~~e3e4e5~~;"|

+

| align=left valign=top style="background:#f7effc;"|

;Brief explanation: Music Blocks is essentially a Logo interpreter. It would be great to be able to export Logo from Music Blocks. (We need to find a Logo that can handle the basic synthesizer needs to make it relevant.)

;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.

Line 206: Line 206:

|-

−

| valign=top width="15%" style="background:#~~f3f4f5;~~"|Sugarizer Primero (Sugarizer1°)

+

| valign=top width="15%" style="background:#fcfcfc"|Sugarizer Primero (Sugarizer1°)

−

| valign=top width="15%" style="background:#~~f3f4f5~~;"|Education Team Caryl Bigenho Samson Goddy Jaskirat Singh perriefidelis

+

| valign=top width="15%" style="background:#fcfcfc;"|Education Team Caryl Bigenho Samson Goddy Jaskirat Singh perriefidelis

−

| align=left valign=top style="background:#~~f3f4f5~~;"|

+

| align=left valign=top style="background:#fcfcfc;"|

;Brief explanation: [https://github.com/llaske/sugarizer Sugarizer] is a large collection of many Activities suitable for general audiences. This project will package a subset of the Activities (Minimum of 10 activites) suitable for children with a target age of 4-7 (grades Pre-K-2) and with a friendly UI/UX experience.

PFidelis

200

edits