Line 72: |
Line 72: |
| === PackageKit control panel plugin for Distribution Activity/OS installs/updates === | | === PackageKit control panel plugin for Distribution Activity/OS installs/updates === |
| | | |
− | The updates Control Panel only deals with updating of user installed Activities and is badly broken with Sugar 0.98. PackageKit is a universal interface to a number of packaging standards (rpm/deb etc) used by a number of distributions. It can work with Fedora/OpenSuse/Debian/Ubuntu and others so provides a single packaging interface to multiple distributions. | + | The updates Control Panel only deals with updating of user installed Activities and is badly broken with Sugar 0.98. PackageKit is a universal interface to a number of packaging standards (rpm/deb etc.) used by a number of distributions. It can work with Fedora/OpenSuse/Debian/Ubuntu and others so provides a single packaging interface to multiple distributions. |
| | | |
| By interfacing with the distribution's packaging interface the user can be displayed with a list of all installed and available Sugar Activities available in the distro, apply Activity and OS updates to their system or install new ones. It allows the distro to have available their Activity set that has been tested and QAed on their platforms. | | By interfacing with the distribution's packaging interface the user can be displayed with a list of all installed and available Sugar Activities available in the distro, apply Activity and OS updates to their system or install new ones. It allows the distro to have available their Activity set that has been tested and QAed on their platforms. |
Line 94: |
Line 94: |
| === End-user modifications of Sugar source === | | === End-user modifications of Sugar source === |
| | | |
− | We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version. | + | We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be created in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version. |
| | | |
| Strong Python skills and experience with Sugar toolkit required. | | Strong Python skills and experience with Sugar toolkit required. |
Line 112: |
Line 112: |
| * Ability to engage and connect with friends and classmates using various Social Networking sites/techniques. | | * Ability to engage and connect with friends and classmates using various Social Networking sites/techniques. |
| * Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.) | | * Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.) |
− | * Separate landing pages for different audiences (kids, teachers, parents, etc) | + | * Separate landing pages for different audiences (kids, teachers, parents, etc.) |
| * Section to share kid created art from projects | | * Section to share kid created art from projects |
− | * Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc). | + | * Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc.) |
| * Ability to have “private classroom spaces” | | * Ability to have “private classroom spaces” |
| * Tools to support community management of the site | | * Tools to support community management of the site |
Line 160: |
Line 160: |
| | | |
| Benefits to the Community: We need to reach out to people who are not yet comfortable with virtual machines et al. by developing less invasive mechanisms for distributing Sugar. | | Benefits to the Community: We need to reach out to people who are not yet comfortable with virtual machines et al. by developing less invasive mechanisms for distributing Sugar. |
− |
| |
− | ===Clean up Ubuntu Sugar packaging===
| |
− | [[File:Tuquito-6-jabber.png|300px]]
| |
− |
| |
− | We have a number of disjointed half-finished or out of date efforts to package Sugar for Ubuntu, including:
| |
− | * https://wiki.ubuntu.com/Sugar (sugar-remix -- deprecated)
| |
− | * http://wiki.sugarlabs.org/go/Sweets_Distribution#Installation (sweets -- Sugar 0.94)
| |
− |
| |
− | This task is to develop a work flow such that Ubuntu becomes part of the Sugar release process, ensuring that Sugar on Ubuntu is current.
| |
− |
| |
− | ''Contact'': [[User:Satellit]]
| |
− |
| |
− | ''Contact'': alsroot on #sugar
| |
− |
| |
− | Level: Advanced
| |
− |
| |
− | Benefits to the Student: Learn about packaging
| |
− |
| |
− | Benefits to the Community: Ubuntu is widely used and we should have our best bits bundled with it in order to reach more potential users.
| |
| | | |
| === Implement help mechanism for activities using Mallard === | | === Implement help mechanism for activities using Mallard === |
Line 233: |
Line 214: |
| | | |
| === GTK wrapper library for Android === | | === GTK wrapper library for Android === |
− | Sugar Activities uses the PyGTK library wich is a binding for GTK. Android doesn't have GTK and porting GTK to Android is very complicated due to the difference in the user space of GNU/Linux and Android.
| |
| | | |
− | The objective of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but invoke equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] wich is the more basic sugar activity. | + | Sugar Activities uses the PyGTK library which is a binding for GTK. Android doesn't have GTK and porting GTK to Android is very complicated due to the difference in the user space of GNU/Linux and Android. |
| + | |
| + | The objective of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but invoke equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] which is the more basic sugar activity. |
| | | |
| Level: Advanced | | Level: Advanced |
Line 376: |
Line 358: |
| | | |
| === ASL Open Video Chat === | | === ASL Open Video Chat === |
− |
| |
| | | |
| Open Video Chat is an Free/Open Source video conferencing activity for the XO laptop. This project was originally started in March 2010 with funding from the National Technical Institute for the Deaf in Rochester NY. | | Open Video Chat is an Free/Open Source video conferencing activity for the XO laptop. This project was originally started in March 2010 with funding from the National Technical Institute for the Deaf in Rochester NY. |
Line 426: |
Line 407: |
| | | |
| Benefits to the Community: By having a [http://wiki.sugarlabs.org/go/Deployment_Platform#Reference_distributions deployment platform] which will be consistent and robust, with an integrated feedback mechanism, Sugar community will enhance feedback loops from deployments. This will help improve Sugar at an accelerated pace. | | Benefits to the Community: By having a [http://wiki.sugarlabs.org/go/Deployment_Platform#Reference_distributions deployment platform] which will be consistent and robust, with an integrated feedback mechanism, Sugar community will enhance feedback loops from deployments. This will help improve Sugar at an accelerated pace. |
| + | |
| + | ===Clean up Ubuntu Sugar packaging=== |
| + | |
| + | [[File:Tuquito-6-jabber.png|300px]] |
| + | |
| + | We have a number of disjointed half-finished or out of date efforts to package Sugar for Ubuntu, including: |
| + | * https://wiki.ubuntu.com/Sugar (sugar-remix -- deprecated) |
| + | * http://wiki.sugarlabs.org/go/Sweets_Distribution#Installation (sweets -- Sugar 0.94) |
| + | |
| + | This task is to develop a work flow such that Ubuntu becomes part of the Sugar release process, ensuring that Sugar on Ubuntu is current. |
| + | |
| + | ''Contact'': [[User:Satellit]] |
| + | |
| + | ''Contact'': alsroot on #sugar |
| + | |
| + | Level: Advanced |
| + | |
| + | Benefits to the Student: Learn about packaging |
| + | |
| + | Benefits to the Community: Ubuntu is widely used and we should have our best bits bundled with it in order to reach more potential users. |