Sugar Labs - User contributions [en]

Summer of Code/2013

2013-03-20T06:02:33Z

RafaelOrtiz: /* IRC Activity fixes */

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

;Note:Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note:Potential students, more project ideas can be found on our [[Features]] page.

__TOC__

=== Write Turtle Blocks in Turtle Blocks ===

In support of making Sugar as transparent and fungible as possible, we'd like to make it not just Free, but provide affordances for end-user modifications. Turtle Blocks is a possible stepping stone towards that end: a programming environment approachable by children as young as five-years old. So as a first step, let's write Turtle Blocks in Turtle Blocks. From that experience, we'll hopefully know how to approach the more general Sugar problem.

''Contact'': [[User:Walter]]

''Co-mentor'':Tony Forster

=== Portfolio videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

''Co-mentor:'' [[User:Aneesh Dogra]]

=== Unified journal view ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandable in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Plugin support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

''Co-mentor:'' [[User:Aneesh Dogra]]

''Co-mentor: '' [[User:Francis]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project sharing website ===

Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

''Co-mentor'': [[User:dogi]]

=== Sugar as a Service website ===

Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
Some features include:
* Ability of integration of [https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp Chrome Remote Desktop]
* Ability to share or to allow other user watch this session
* Ability to scale the infrastructure onto local (virtualbox}, private (kvm) and other public clouds (http://fedoraproject.org/wiki/Cloud_SIG, http://xvm.mit.edu/ or http://cloud.ubuntu.com/)

''Contact'': [[User:dogi]]

''Co-mentor'': [[User:Aneesh Dogra]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into our i18n / L10n system.

''Contact'': [[User:Walter]]

''Co-mentor'': [[User:Aneesh Dogra]]

''Co-mentor'': [[User:Francis]]

=== IRC Activity fixes ===

* [[Activities/IRC]] is built around an all-Python IRC client, [http://urk.sourceforge.net/ Urk] which is no longer maintained since 2007. Thus, its better to port the activity to a newer and a better all-python IRC library.
* [[Activities/IRC]] is significantly slower than other IRC clients available on other platforms. The reason being its not multi-threaded. Thus, adding multi-threading support will be very useful.
* [[Activities/IRC]] is missing some useful features including sound on highlight (play a sound when the user is highlighted in a channel), user info (whois data) and many others. Look at some popular IRC clients running on other platforms and research about the features which can be added to [[Activities/IRC]] and how can they be added.

Requires familiarity with Python and IRC protocol specifications.

''Mentor'': [[User:Aneesh Dogra]]

''Co-mentor'': [[User:RafaelOrtiz]]

=== Activity Development Framework ===

This framework should allow to:
* Make toolbars from factories removing many lines of code.
* Start a project through typing a command.
* Doing collaboration easier to implement.
* Any other work which makes the development process hard and can be framed.

''Contact'': [[User:Francis]]

=== ASLO Enhancements ===

The current [http://activities.sugarlabs.org/ Activity Library] is based in an old version of the [http://addons.mozilla.org/ Mozilla Add-ons Library].

This project is divided in three parts:

* Update the old platform and have the corresponding modifications to distribute Sugar Activities instead of Mozilla Plugins.
* Add an activity manager to the control panel. Allowing the installation/update of activities from ASLO.
* Add to the Sugar Bundle Builder a way to auto-upload activities to ASLO.

''Contact'': [[User:Francis]]
=== Chat Activity with translation ===
[[File:Chat.JPG|300px]]
*'''Above ^ Example of a chat where to 2 people connected by chat could not talk to each other.'''
: Due to language barrier
*Add a drop-down box that translates of the chat messages coming from another user.
:Similar to the private/shared drop down shown.
*This could work like the #sugar / #sugar-es channels on IRC
''Contact'': [[User:Satellit]]

''Co-mentor'': [[User:Aneesh Dogra]]

===Stereo data capture in Turtleart and Measure===
Stereo input is supported by XO-1.5, 1.75 and 4 hardware but is disabled due to buggy software. (Could you please elaborate - Aneesh)

This is a possible project, if not too difficult.

Possible mentors

Tony Forster

Walter (if he is OK with it)

Summer of Code/2013

2013-03-18T22:54:43Z

RafaelOrtiz: interest in being mentor

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

;Note:Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note:Potential students, more project ideas can be found on our [[Features]] page.

__TOC__

=== Write Turtle Blocks in Turtle Blocks ===

In support of making Sugar as transparent and fungible as possible, we'd like to make it not just Free, but provide affordances for end-user modifications. Turtle Blocks is a possible stepping stone towards that end: a programming environment approachable by children as young as five-years old. So as a first step, let's write Turtle Blocks in Turtle Blocks. From that experience, we'll hopefully know how to approach the more general Sugar problem.

''Contact'': [[User:Walter]]

=== Portfolio videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

''Co-mentor:'' [[User:Aneesh Dogra]]

=== Unified journal view ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandable in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Plugin support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

''Co-mentor:'' [[User:Aneesh Dogra]]

''Co-mentor: '' [[User:Francis]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project sharing website ===

Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

''Co-mentor'': [[User:dogi]]

=== Sugar as a Service website ===

Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
Some features include:
* Ability of integration of [https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp Chrome Remote Desktop]
* Ability to share or to allow other user watch this session
* Ability to scale the infrastructure onto local (virtualbox}, private (kvm) and other public clouds (http://fedoraproject.org/wiki/Cloud_SIG, http://xvm.mit.edu/ or http://cloud.ubuntu.com/)

''Contact'': [[User:dogi]]

''Co-mentor'': [[User:Aneesh Dogra]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into our i18n / L10n system.

''Contact'': [[User:Walter]]

''Co-mentor'': [[User:Aneesh Dogra]]

''Co-mentor'': [[User:Francis]]

=== IRC Activity fixes ===

* [[Activities/IRC]] is built around an all-Python IRC client, [http://urk.sourceforge.net/ Urk] which is no longer maintained since 2007. Thus, its better to port the activity to a newer and a better all-python IRC library.
* [[Activities/IRC]] is significantly slower than other IRC clients available on other platforms. The reason being its not multi-threaded. Thus, adding multi-threading support will be very useful.
* [[Activities/IRC]] is missing some useful features including sound on highlight (play a sound when the user is highlighted in a channel), user info (whois data) and many others. Look at some popular IRC clients running on other platforms and research about the features which can be added to [[Activities/IRC]] and how can they be added.

Requires familiarity with Python and IRC protocol specifications.

''Contact'': [[User:Aneesh Dogra]]

''mentor'': [[User:RafaelOrtiz]]

=== Activity Development Framework ===

This framework should allow to:
* Make toolbars from factories removing many lines of code.
* Start a project through typing a command.
* Doing collaboration easier to implement.
* Any other work which makes the development process hard and can be framed.

''Contact'': [[User:Francis]]

=== ASLO Enhancements ===

The current [http://activities.sugarlabs.org/ Activity Library] is based in an old version of the [http://addons.mozilla.org/ Mozilla Add-ons Library].

This project is divided in three parts:

* Update the old platform and have the corresponding modifications to distribute Sugar Activities instead of Mozilla Plugins.
* Add an activity manager to the control panel. Allowing the installation/update of activities from ASLO.
* Add to the Sugar Bundle Builder a way to auto-upload activities to ASLO.

''Contact'': [[User:Francis]]
=== Chat Activity with translation ===
[[File:Chat.JPG|300px]]
*'''Above ^ Example of a chat where to 2 people connected by chat could not talk to each other.'''
: Due to language barrier
*Add a drop-down box that translates of the chat messages coming from another user.
:Similar to the private/shared drop down shown.
*This could work like the #sugar / #sugar-es channels on IRC
''Contact'': [[User:Satellit]]

''Co-mentor'': [[User:Aneesh Dogra]]

Features/Transfer to many options

2012-04-12T19:37:54Z

RafaelOrtiz:

=== Proposal for a client-initiated journal transfer (1-to-N feature) ===

== Workflow ==

* The server XO would make its shares available via WebDAV, running in the context of "httpd" service.
* The client XO would connect to the server XO via its browser.
* Therafter, "Browse" would take over.

== Details ==

* '''Setting up WebDAV on a server XO.'''
** Install package "httpd".
** Generate openssl "server.crt" and "server.key".
<code>cd /etc/ssl/certs/</code>
<code>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</code>
** Configure "/etc/httpd/conf.d/ssl.conf" to setup the WebDAV share. Sample file : [[media:ssl.conf]]
*** Firstly, this sets up the paths "SSLCertificateFile" and "SSLCertificateKeyFile", which are required for HTTPS over SSL.
*** Secondly, sets up "/var/www/web1/web" as the "webdav" folder. In other words, whetever entries are present in this folder, will be made available for the client XOs.
** Generate authentication file for the webdav folder. These user-password credentials will be asked whenever a client tries to access the webdav folder. For example, the following list of commands sets "test" as the user, and "olpc" as the password.
<code>sudo htpasswd -c /var/www/web1/passwd.dav test
New password: <olpc>
Re-type new password: <olpc>
Adding password for user test</code>
** Start service "httd".
** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE.

* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
** Sascha's JournalToWebDAV workflow.
*** step 1
*** step 2
*** step 3
*** step 4
** Alternatively,
*** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share.
*** "Share" would follow all the schematics of "Documents" type. After all, "Share" is just a folder in the filesystem (like "Documents").
*** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf").
*** All entries in the "Share" folder would be available to client XOs.

* '''[Code-Requirements] Exporting Data to WebDav, on a server XO.'''
** Sascha has already coded the first alternative.
** For the second alternative, "Share" listview needs to be added on the lines of "Documents" listview. Code-reuse should be done as much as possible. Ideally, there should just be a difference of the "folder-path".

* '''[User-Workflow] Client XO wishes to access the share of Server XO.'''
** Navigates to the "Neighborhood" view.
** Hovers over the "Server" buddy.
** The popup appears, which has a new entry "Access Share" (in addition to "Make Friend").
** Clicks on "Access Share".
** The "Browser" activity opens, with the url pointing to the "Server" buddy's webdav share.
** Thereafter, client may navigate the webdav directory hierarchy, or download files (all of which is already built in the "Browse" activity). Most importantly, there is the "Keep Link" feature in "Browse", which nicely downloads the webdav-entry, and promptly saves it in the "Journal" - something that happens in the "Send To" feature as well.

* '''[Code-Requirements] Client XO wishes to access the share of Server XO.'''
** Mapping a neighborhood-buddy to its IP Address
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist it in the "BaseBuddyModel" in "jarabe/model/buddy.py".
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
** Opening up the server's webdav
*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html. (For resolving this, some additional code may have to be written, but that is something perfectly doable. However, currently awaiting a reply, to see if the code for this already exists :-) ).

== SCREENSHOTS ==

=== SERVER has initially empty "Shares" icon in bottom tray. ===
** [To be decided] Is "Shares" the correct terminology ?
** [To be decided] Icon for "Shares".

**[[File:S1.png]]

=== CLIENT clicks on "Access Shares" in Neighborhood View. ===

**[[File:S2.png]]

=== CLIENT enters the SERVER username and password in the opened "Browse" instance. ===

**[[File:S3.png]]

=== CLIENT sees nothing shared as the SERVER has not shared anything yet. ===

**[[File:S4.png]]

=== SERVER copies data to "Shares". ===

**[[File:S5.png]]

=== SERVER now has some entries in "Shares" directory. ===

**[[File:S6.png]]

=== CLIENT clicks the refresh button in "Browse". ===

**[[File:S7.png]]

=== CLIENT is now able to see the SERVER's "Shares" listing. ===

**[[File:S8.png]]

=== CLIENT right clicks on the entry that she wishes to download and selects "Keep Link". ===

**[[File:S9.png]]

=== CLIENT Download completed. ===

**[[File:S10.png]]

=== CLIENT downloaded entry in Journal. ===

**[[File:S11.png]]

== [ARCHIVE] Possible options ==

In a server-initiated operation, the server is responsible for adequate delivery to all the clients, whatever the number may be.
In a client-initiated operation, each client is responsible for herself only.

{| class="wikitable"
|-
! Option
! Server-Initiated / Client-Initiated
! Secure Data Transfer
! Proxy Support
! Peer to Peer Support (Gabble/Salut)
|-
| Looping over "Send To"
| Server-Initiated
|
|
| Yes/Yes
|-
| Sascha's JournalToWebDAV
| Client-Initiated
|
|
|
|-
| Each XO acts as an independent WebDAV server; client uses browser
| Client-Initiated
| Yes (HTTPS over SSL)
|
| /Yes
|}

Activities/GeoGebra

2012-03-20T17:21:34Z

RafaelOrtiz: /* Try development version */

== Overview ==

GeoGebra is free and multi-platform dynamic mathematics software for all levels of education that joins geometry, algebra, tables, graphing, statistics and calculus in one easy-to-use package. It has received several educational software awards in Europe and the USA.

'''Quick Facts'''

* Graphics, algebra and tables are connected and fully dynamic.
* Easy-to-use interface, yet many powerful features.
* Authoring tool to create interactive learning materials as web pages.
* Available in many languages for our millions of users around the world.
* Free and open source software.

== Tips ==

=== Try development version ===

* [[#Resources|Install]] GeoGebra by the regular way;
* Download {{Code|.jar}} files for development version, e.g., for [http://www.geogebra.org/webstart/4.2/unpacked/ current beta], place them to {{Code|~/Activities/GeoGebra.activity/geogebra}} directory and restart Sugar.

=== Re-bundle activity ===

* [[#Resources|Install]] GeoGebra by the regular way;
* from {{Code|~/Activities/GeoGebra.activity}} directory, run {{Code|./setup dist_xo}} command to create new {{Code|.xo}} bundle in {{Code|dist/}} directory.

== Resources ==

* [http://www.geogebra.org/cms/ Home page].
* [[Activity Library]] [http://activities.sugarlabs.org/en-US/sugar/addon/4284 download page].
* [http://www.geogebratube.org/ GeoGebraTube], official repository of GeoGebra constructions and GeoGebra related resources.

Summer of Code/2012

2012-02-29T16:21:24Z

RafaelOrtiz:

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note: Potential mentors, please feel free to add ideas to this list.'''

'''Note: Potential students, more project ideas can be found on our [[Features]] page.'''

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a robotics plugin for Turtle Art ===

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-02-29T16:20:09Z

RafaelOrtiz: /* = Implement a robotics plugin for Turtle Art */

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note: Potential mentors, please feel free to add ideas to this list.'''

'''Note: Potential students, more project ideas can be found on our [[Features]] page.'''

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

== Implement a robotics plugin for Turtle Art ==

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-02-29T16:07:00Z

RafaelOrtiz: new proposed idea.

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note: Potential mentors, please feel free to add ideas to this list.'''

'''Note: Potential students, more project ideas can be found on our [[Features]] page.'''

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

=== Implement a robotics plugin for Turtle Art ==

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-02-24T05:25:14Z

RafaelOrtiz: /* Project candidates */

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note: Potential mentors and participants, please feel free to start adding things to this list.'''

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-02-24T04:53:50Z

RafaelOrtiz: /* Project candidates */

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note: Potential mentors and participants, please feel free to start adding things to this list.'''

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

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

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* 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.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* 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 to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the execises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Dextrose/3/activites

2012-02-23T15:27:48Z

RafaelOrtiz: /* org.tuxpaint Tux Paint MIA */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: OLPC team is making a webkit porting
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes: In Stable release
*Maintainer: Ariel
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes: In stable Release.
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint ===
*Notes: New releases by AC to account bugs.
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/Ben/Dirakx)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Dirakx)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:27:13Z

RafaelOrtiz: updates

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: OLPC team is making a webkit porting
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes: In Stable release
*Maintainer: Ariel
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes: In stable Release.
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/Ben/Dirakx)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Dirakx)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:25:58Z

RafaelOrtiz: /* ClassroomViewer */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: OLPC team is making a webkit porting
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes: In Stable release
*Maintainer: Ariel
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes: In stable Release.
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:25:41Z

RafaelOrtiz: /* ClassroomBroadcast */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: OLPC team is making a webkit porting
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes: In Stable release
*Maintainer: Ariel
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes:
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:25:02Z

RafaelOrtiz: /* org.laptop.WebActivity Browse */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: OLPC team is making a webkit porting
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes:
*Maintainer
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes:
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:24:39Z

RafaelOrtiz: /* org.laptop.WebActivity Browse */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Webkit porting.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes:
*Maintainer
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes:
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:23:28Z

RafaelOrtiz: /* org.worldwideworkshop.PollBuilder Poll MIA? */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes:
*Maintainer
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes:
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll===
* Ac has helped in doing new version 11 to fix bugs.

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2012-02-23T15:21:30Z

RafaelOrtiz:

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person:
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:
*Maintainer: Gonzalo.
*Status:
*Bugs:

=== ClassroomBroadcast ===

*http://activities.sugarlabs.org/en-US/sugar/addon/4507
*Notes:
*Maintainer
*DX person: Ariel

=== ClassroomViewer===
*http://activities.sugarlabs.org/en-US/sugar/addon/4527
*Notes:
*Maintainer: Ariel
*DX person: Ariel

== 2. Priority ==

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person:
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person:
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Talk:Features/WebKit/Development

2012-01-24T03:09:52Z

RafaelOrtiz: Created page with "* About the stop button, we should assure that if the download is stopped either by clicking the button or by connection stopped, the partial downloaded file gets cleaned along w..."

* About the stop button, we should assure that if the download is stopped either by clicking the button or by connection stopped, the partial downloaded file gets cleaned along with cache.

Activities/Classroom Broadcast

2011-12-21T21:26:38Z

RafaelOrtiz:

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as [http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page TigerVNC] runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from

*http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install '''x11vnc''' enter the following in Terminal:

sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:

sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

== Todo ==

*Add i18n and l10n

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py

----

Must be fixed by v3 http://activities.sugarlabs.org/downloads/file/27762/classroombroadcast-3.xo --[[User:RafaelOrtiz|RafaelOrtiz]] 12:10, 28 November 2011 (EST)

----

* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Features/GTK3

2011-12-20T19:17:50Z

RafaelOrtiz: /* HippoCanvas removal */

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

== Summary ==

'''Sugar needs to rebase itself on new generations of its key underlying technologies: GTK+ 3 and PyGObject Introspection.''' Sugar is already somewhat broken on recent distribution versions as a result of this. This page aims to summarise options and community opinions around this challenging shift, and to help formulate a plan of how it will be executed. In other words, it tries to take community input, answer all the unanswered questions, and present a logical path forward that can be adopted by the developers.

== Owner ==
* This plan/proposal maintained by [[User:DanielDrake|Daniel Drake]] (other editors welcome!)
* A number of developers will be needed at each stage to successfully execute this; Daniel offers his assistance for a coordination/oversight role if that would be useful.

== Current status ==
* Targeted release: 0.96 (at least for sugar-toolkit port)
* Last updated: (DATE)
* Percentage of completion: XX%

At the Desktop summit, Raul Gutierrez Segales, Benjamin Berg and Paul Proteus successfully [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg22070.html prototyped] some of the ideas below. After only a few hours of effort, a minimal Sugar GTK3 activity was running alongside GTK2 activities. The plan below should therefore be quite credible, but some prerequisites remain.

== Detailed Description ==

Two major changes have recently occurred in Sugar's underlying technologies. Firstly, GTK+ 2 has been obsoleted by GTK+ 3, and GNOME is now based on GTK+ 3. Secondly, [http://pygtk.org/ PyGTK], the underlying Python library that Sugar uses to call into GTK+, has been deprecated in favour of [http://live.gnome.org/PyGObject/IntrospectionPorting PyGObject Introspection] (hereafter "PyGI").

In order to remain innovative and current, and to take advantage of the latest developments, Sugar needs to follow suit and move to GTK3 and PyGI. Lagging behind on this conversion is already bringing negative consequences to Sugar; notably 2 of our most important activities (Read and Browse) are already broken and without a future until we catch up again.

Unfortunately, this is an API-incompatible change. As confirmed by the PyGI developers, PyGTK and PyGI cannot be mixed in the same process. This means that the conversion process can't be done on a fine, incremental basis, and if sugar-toolkit were to be simply replaced with a PyGI/GTK3 port, this means that all existing activities would stop working until they themselves have also been ported - all activities will need modifications as part of this feature. The community has expressed desire for old activities to continue working (many are unmaintained); unfortunately this is not realistic in the long term. As a compromise, this feature discussion includes the requirement that for a certain period of time, both PyGTK/GTK2 and PyGI/GTK3 activities must be able to function alongside each other. As detailed below, this can be pulled off quite easily and in a way that will not drain resources.

This project will involve modifications to almost every file within Sugar and its activities, making it a huge task, even though the vast majority of code is trivial to port. This feature discussion attempts to identify ways that this porting process can be done in distinct stages, where Sugar remains functional at the completion of each stage, making this more manageable.

For the most part, the port from PyGTK to PyGI only involves changing the names that are used to access methods and constants. PyGI uses a slightly different and more consistent naming scheme to wrap GTK+.

import gtk
gtk.MessageDialog(None, 0, gtk.MESSAGE_INFO, gtk.BUTTONS_CLOSE, "Hello World").run()

The above PyGTK code rewritten as PyGI is:

from gi.repository import Gtk
Gtk.MessageDialog(None, 0, Gtk.MessageType.INFO, Gtk.ButtonsType.CLOSE, "Hello World").run()

PyGI provides a script which can be used to automate much of the conversion.

The move from GTK2 to GTK3 is also expected to be unproblematic, because the vast majority of code does not need any changes - most GTK3 API/ABI is identical to GTK2. The cases which do require some intervention to solve will take some time, but the changes are [http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html well documented] and the number of cases encountered should be low.

== Benefit to Sugar ==

# PyGI is technologically better than PyGTK. It is a nicer way of calling into GObject-style libraries from Python that means less maintenance is needed upstream (PyGObject automates the creation of bindings to a degree much higher than PyGTK ever could, and automatically achieves more complete coverage).
# PyGTK is no longer maintained; PyGI is actively maintained.
# The move to GTK3 allows us to [http://blog.tomeuvizoso.net/2011/05/time-to-port-your-python-application-to.html keep up with our GNOME neighbours], as they improve and refine the base technologies that we share.
# The move to PyGI is expected to result in [http://blog.tomeuvizoso.net/2009/05/reducing-sugars-memory-usage.html lower memory usage and faster startup].
# Browse has no future under GTK2 and is '''already broken''', it [[Features/WebKit|needs to move to WebKit]] and that move is dependent on Sugar moving to PyGI/GTK3.
# Similarly, Read is '''already broken''' under GTK2 due to static evince bindings no longer being maintained and libevince itself moved to GTK3; we need to switch to PyGI/GTK3 to be able to keep calling into evince and let the Read activity live on.

== Implementation Plan ==

Sugar is divided into different components, many of which run in different processes. This means that we are able to divide up the required work on a process-by-process basis. While this work is being conducted, some Sugar processes might be based on PyGI/GTK3 and others based on PyGTK/GTK2, but the platform would keep functioning at each stage. There would be some system resource overhead during this transitional time (as the system would need to have PyGTK, GTK2, PyGI and GTK3 all in memory) but this feature implementation would end with the whole sugar ecosystem using PyGI/GTK3.

=== HippoCanvas removal ===

A prerequisite to porting a Sugar process, component or activity is to remove all its usage of hippocanvas. This library is unmaintained, would be painful to port to GTK3, and can be done better with standard GTK+ code at the Python level. Most users of HippoCanvas can switch to custom GtkContainer widgets.

One complication is that hippo usage is not limited to Sugar's core; some activities use hippo, or they pull on sugar-toolkit classes which are implemented with hippo. These are: Chat, Speak (please list others here).

=== Theme porting ===

[[/Theme|Theme status.]]

One major internal change in GTK3 is the way that themes are designed. GTK2 allowed themes to be implemented with a special format in a gtkrc file, but GTK3 now requires that themes are implemented using CSS. Therefore another non-trivial prerequisite for a GTK3-based sugar release of any visual component is the porting of the theme.

Fortunately, the gtkrc file format does not seem to be too far away from css (i.e. it applies attributes to classes in a textual format), and css is well known and well documented, so hopefully this is not a major challenge. For an example of the old GTK2 style, see <tt>/usr/share/themes/Adwaita/gtk-2.0/gtkrc</tt>, and for a GTK3 CSS example see <tt>/usr/share/themes/Adwaita/gtk-3.0/gtk-widgets.css</tt>

=== Backwards-compatibility for activities ===

As mentioned above, as mixing PyGTK/GTK2 and PyGI/GTK3 is impossible, a straightforward port of sugar-toolkit to PyGI/GTK3 would break all activities. However, having backwards compatibility for activities for a limited time is considered a requirement, and having a "flag day" where all activities stop working until ported is not seen as an option - there must be a transition period.

As the conversion process from PyGTK to PyGI makes minor changes to almost every single line of code that involves GTK/glib, maintaining both PyGI and PyGTK codepaths in the same files is not realistic (there would be an unrealistic amount of <tt>if</tt> conditions). We are therefore required to have two copies of sugar-toolkit during the transition period: one for ported PyGI/GTK3 activities, and another for PyGTK/GTK2 activities that have not yet been ported.

As we do not have plentiful developer resources, I propose that the PyGTK/GTK2 version of sugar-toolkit is frozen as soon as this feature development is underway. No bugfixes or improvements, just a copy of the code at that point.

The GTK3 version of sugar-toolkit would be installed under a new module named sugar1, distinguishing it from the frozen GTK2 sugar version to be removed later. All code will need extensive textual changes in moving to GTK3, changing "import sugar.foo" to "import sugar1.foo" will just be another step in that process.

The removal of the GTK2 sugar-toolkit version would happen one year after the first stable release of a sugar-toolkit that includes GTK3 support. In this context, 'removal' means that it gets deleted from the sugar-toolkit master branch of the git tree. Old versions of sugar-toolkit will of course be left available, in old git branches and release tarballs.

=== Proposed plan of action ===

The steps below prioritise the porting of sugar-toolkit, as this is where Sugar would see the most immediate benefit: the revival of Browse and Read. The steps that follow can largely be parallelised; the important bit is placing sugar-toolkit first in line.

# Remove hippocanvas from sugar-toolkit
# Port sugar theme to GTK3
# Port sugar-toolkit to GTK3 while keeping backwards compatibility, release as sugar-toolkit-0.95.x
# Rescue Browse and Read, and allow independent activity porting efforts to begin
# Remove hippocanvas from all other parts of Sugar, including activities
# Port Sugar core to GTK3
# Remove sugar-toolkit's GTK2 compatibility one year after the first GTK3 sugar-toolkit stable release

=== How to port ===

I plan to start a page at [[Features/GTK3/Porting]] that details the porting process, that could be provided as documentation to anyone involved in these efforts (including those working on porting Sugar core, but also those working on activities). The content covered will be:

# How to remove hippo and what to replace it with (links to commits that have done this for other activities, etc)
# How to select the GTK3 version of sugar-toolkit
# How to handle each of the sugar-toolkit API changes (detailed in the following section)
# How to port from PyGTK/GTK2 to PyGI/GTK3.
#* This basically involves reading the [https://live.gnome.org/PyGObject/IntrospectionPorting PyGObject porting documentation], using pygi-convert.sh, then checking the result.
#* The [http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html Migrating from GTK+ 2.x to GTK+ 3] should also be read.

== Other considerations ==

=== Version number ===

It goes without saying that such a migration would be the basis of a new major release. When this topic has been discussed before, people have toyed with the idea of calling the GTK3 version of Sugar "Sugar-1.0".

There are arguments for:
* This is undoubtedly a paradigm shift for Sugar, so a major bump to the version number is called for.
* It would make the change really obvious

And there are arguments against:
* Some people might interpret the number 1.0 as indicating a higher level of maturity than what the developers feel
* Some developers have very specific ideas about what should be included in Sugar-1.0, even if development of such items is barely even on the horizon
* Some people want a much longer lead-up time to Sugar-1.0 so that the API can be refined/reworked/perfected

Tomeu, Simon and Marco agreed that the 1.0 version number could be used here, and communicated in a slightly different sense: "we are really still in the first iteration and 1.0 will be when that first iteration reaches maturity, without big changes in the API. After 1.0 we can start working on what will be one day 2.0 which should be the second iteration of Sugar, hopefully using what we have learned during these years."

However, current Sugar developers feel strongly that the changes described here are not significant to warrant a major version bump and have specific ideas about what should be included in a 1.0 release. Therefore, in the interest of being slightly less intrusive, this feature does not ultimately propose a version numbering change - it is planned that sugar-toolkit-0.96 will be released as the first with GTK3 support, and once we reach sugar-0.98, the next releases will be 0.100, 0.102, etc.

=== Retaining the 'sugar' module name ===

The strategy suggested above involves the GTK3 sugar-toolkit version being installed with the 'sugar1' module name. It would be possible to retain the 'sugar' name for this module via a Python trick documented below, but it appears that there is no demand for this from the community. Porting to GTK3 requires major textual changes anyway, changing 'sugar' to 'sugar1' in the same files is therefore regarded as acceptable. Here is how the naming trick could be done anyway:

* The new GTK3 version of sugar toolkit would be installed with name <tt>sugar</tt>, and the old GTK2 version would be installed with name <tt>sugar_gtk2</tt>.
* Before <tt>sugar-activity</tt> imports sugar.activity (or any other sugar-toolkit class), it would look for an empty file called "GTK3_PORTED" in the activity's directory. If present, it would run a little trick:
import os
import sys
if not os.path.exists("GTK3_PORTED"):
import sugar_gtk2
sys.modules["sugar"] = sugar_gtk2
* The result is that all unported/unmodified activities (without the GTK3_PORTED file) would <tt>import sugar.foo</tt> as before, but the above trick that modifies Python's module table would result in them (transparently, magically, automatically) being redirected to sugar_gtk2.foo.
* At the end of the transition period, sugar_gtk2 would be deleted in entirity, the above addition to sugar-activity would be dropped, and activities could drop the GTK3_PORTED files at their leisure.

Further consideration would need to be given to sugar-base. This package installs some classes which are then used by sugar-toolkit, so they would need to be duplicated into sugar_gtk2.

=== Python 3 ===

Is it worth throwing in a Python 3 migration into this project? I have researched the issue, and my opinion is: no.

* Python 3 brings no immediate obvious benefit, and does not fix any pressing problems. On the other hand, PyGI solves some clear breakage for us.
* Python 3 (or rather the code that supports it) is not mature. Many modules are still Python2-only.
* PyGI does support Python 3, but it was [http://mail.gnome.org/archives/python-hackers-list/2011-July/msg00000.html broken] when I tried it. It is not seeing much attention.
* Our neighbours within GNOME and other open source projects are only just starting to play with Python 3. There is not much similar experience we can build upon. There may be teething problems, such as modules that Sugar uses that haven't been ported, and bugs in existing ports due to lack of use (such as the fact that PyGI was broken for quite a while with nobody noticing) that hold us back. This is not so for the PyGI transition, where we can look at many PyGTK applications that have been ported and that are actively used.
* J5 (PyGI developer) suggested that we avoid combining the 2 migrations. It would add more change to an already disruptive project, and increases the risk. It would be better to limit the amount of change we introduce, so that risk is more manageable and to decrease the number of problems and challenges that we face.
* If the above situation does change, the Python 3 migration will be much easier than this one. Py3 migration does not require invasive code changes. It will be much easier to have Python 2 and 3 support maintained in parallel. The few existing projects that have done this are able to maintain Python2 and Python3 support in the same codebase, without too many if conditions. The "if we're already making so much change, why not avoid a future migration period by including Py3" argument is not very strong, because the Py3 migration will be much smoother and less complex.

== API changes ==

The fact that almost all Sugar components and activities require sweeping changes as part of this shift presents an interesting opportunity for us to make API changes in sugar-toolkit. The importance here should still be placed on the technology shift, rather than on the opportunity to produce a perfect API (which we could spend all eternity designing and discussing), but this is an opportunity that we should not miss.

I propose that once sugar-toolkit is ported and mostly operational, we run a 30-day window where API changes that have seen some kind of planning and discussion below can be made and committed.

=== Plain text as the default for palettes ===

Sugar's palette classes currently accept strings, but then they pass those strings to GTK as markup (always, unconditionally). However, markup is only used in a handful of places, and this means that all users of palettes that draw in translations or strings from other sources which might contain characters such as < or > must escape their arguments, leading to big patches [http://article.gmane.org/gmane.comp.education.sugar.devel/32398 like this].

As agreed [http://article.gmane.org/gmane.linux.laptop.olpc.sugar/30466 here], it would make more sense for palettes to pass those strings as standard text by default, and to have different functions to opt-in to receive markup processing. Then the excessive escaping would go, and the only users would have to escape would be those who use markup.

=== Removal of keep button ===

Sugar-0.94 proposes the [http://article.gmane.org/gmane.linux.laptop.olpc.sugar/30771 removal of the Keep button], but the old KeepButton classes would be kept around for activities that directly use it. Porting sugar-toolkit to GTK3 would be a good time to remove these classes.

=== Removal of old toolbars ===

Sugar-0.86 [[Features/New_Toolbar_Design|redesigned activity toolbars]], with the new toolbars implemented by new classes, and the old classes being kept around so that old activities are not immediately broken. This would be a good opportunity to remove the long-deprecated old activity toolbar classes.

== Dependencies ==

Sugar would start depending on PyGObject built with gobject introspection support, GTK3, and (at the end of the transition period) would drop its dependencies on GTK2 and PyGTK.

== Contingency plan ==

Hopefully, this page has been convincing in that this change is of necessity. Either way, we should consider our options for the case where this migration is found to be more difficult than predicted.

As this migration would take over the course of a major release (or perhaps 2-3 of them, as components are ported individually), our users have the option to remain on older releases in the face of stability issues, and as developers we have the option of delaying major releases until things are ready.

If new PyGI/GTK3-based major releases are found to be unstable, we also have the option of allowing interested community members to pick up maintenance of older GTK2-based release branches (e.g. 0.94) with a "master first" commit policy. Personally, I would suggest that it would be a better use of resources to have those people help fix any problems with the GTK3 version, but as an open source community this is something we must be open to.

In the event of problems in the GTK3 version of sugar-toolkit, activity authors have the (default) choice of staying with GTK2. The transition period before the GTK2 version is removed would obviously be extended in the face of significant problems with GTK3 version.

== Documentation ==
* [[Features/GTK3/Development | Development page]]
* [[Features/GTK3/Porting | Activity porting guide]]

== Release Notes ==

== Hackfests ==

This work would benefit from some focused attention at in-person meetings.

See [[Features/GTK3/DesktopSummitActivities]] for earlier desktop summit ideas.

On September 10th-12th, a SugarCamp will be held in Paris. We will be working on this plan at the event, starting with the prerequisites.

On October 28th-30th, a hackfest will be held in Prague with the specific purpose of implementing this plan: [[Marketing_Team/Events/Gtk3_Hackfest_2011]]

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
== Subpages ==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Activities/TamTam

2011-12-20T19:15:26Z

RafaelOrtiz: /* Bundling from Sweets */

<noinclude>[[Category:Activities|Tam Tam]]</noinclude>
==Tam Tam developers' page==

===Overview===

TamTam is a suite of four music and sound related activities for the XO. TamTam is written in python with some C functions for speed-critical services. The audio engine for TamTam is Csound.

=== Build from sources ===

In Terminal activity, launch:

sudo yum install git csound-devel alsa-lib-devel python-devel make gcc-c++

Clone the sources and build binaries:

mkdir -p ~/Activities
git clone --depth 1 git://git.sugarlabs.org/tamtam/tamtam.git ~/Activities/tamtam
cd ~/Activities/tamtam/common/Util/Clooper
make

If make was successful, create symlinks to all TamTam activities:

cd ~/Activities/tamtam
./setup.py dev

== Bundling from Sweets ==

If you are using [[Platform_Team/Sweets|Sweets]] you can bundle your changes with:

sweets bind sdk/sugar ./setup.py dist_xo

This can be done in the root of tamtam sources

==Resources==

* [[Tam Tam Resources]] - Learner resources
* [http://git.sugarlabs.org/projects/tamtam-branch Sources]
* Sugar Activity Library pages:
** [http://activities.sugarlabs.org/en-US/sugar/addon/4059 TamTamEdit]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4060 TamTamJam]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4061 TamTamMini]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4062 TamTamSynthLab]
* [[olpc:TamTam|TamTam on OLPC wiki]]
* Trac tickets: [http://dev.laptop.org/query?component=tamtam-activity&col=id&col=summary&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority OLPC], [http://bugs.sugarlabs.org/query?component=TamTam&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs]

Platform Team/Sugar Network/Architecture

2011-12-19T22:00:12Z

RafaelOrtiz: typo

This page is an overview of technical implementation of the Sugar Network. See also the [[Sugar_Network|introduction page]] and the [[Sugar_Network/Concept|basic concepts overview]].

== Summary ==

The technical decisions are tailored by:

* Real needs of deployments like [[Deployment_Team/Peru/Puno#The_problem|one-teacher schools in Peru]] and should be as simple as possible;
* The system, from users point of view, should just work proving high-level services that cover the full collaboration circle that should exist within Sugar learning community;
* The system should be useful not only for off-line environments, but also for cases in decent Internet connection.

== Overview ==

[[File:Sugar-networks-architecture.png|right]]

The Sugar Network consists of different types of components:

* [[#Server|Server side]] that provide [[Platform_Team/Sugar_Network/API|API]] for clients:
** [[#Mothersip|Mothership]] server that keeps the whole Sugar Network information, clients might connect directly to this server (on-line case) or indirectly via distributed servers (off-line case);
** Optional [[#Distributed_servers|distributed servers]], contain a [[#Synchronisation|synchronised]] copy of central server (might be not for the entire Network to save storage space);
* [[#Client|Client side]]:
** Client application that uses [[Platform_Team/Sugar_Network/API|API]] to interact with a server;
** Client application that [[#Personal_server|provides]] limited [[Platform_Team/Sugar_Network/API|API]] to support server-less workflow.

== Server ==

In all cases the server [[Platform_Team/Sugar_Network/API|API]] is the same for clients. But depending on connectivity, clients might be connected to the [[#Mothership|Mothership]] or to an [[#Distributed_servers|intermediate server]].

=== Mothership ===

The place where data is being collected from all distributed server. If clients have connectivity, they can connect to the Mothership to contribute to the Network directly.

=== Distributed servers ===

Servers that will be useful if:

* there is no connectivity at all;
* connectivity is sporadic;
* connectivity is not cheap and its usage needs to be minimized.

Distributed services provide full featured [[Platform_Team/Sugar_Network/API|API]] as the Mothership does. Distributed servers need to be [[#Synchronisation|synchronized]].

=== Synchronisation ===

To let Network participant, connected to particular [[#Distributed_servers|distributed server]], interact with people from another distributed servers or with people from the Internet, distributed servers need to be synchronized.

Server might be synchronised:

* With the Mothership, if connectivity presents;
* With the Mothership or any other distributed servers via the [[Wikipedia:Sneakernet|Sneakernet]].

== Client ==

Client application is local, for reasons:

* Originally, Sugar Network was being developed for deployments where teachers' XOs will be distributed servers, thus, it will be useful to delegate some of computing to students' XOs;
* Stimulate doing behaviour when it should be possible to create new client application or tweak existing on a client side;
* It is all time possible to create Web application on a server side.

=== Default client ===

The default client is implemented using Web technologies to:

* Using Web technologies might make client developing easier;
* Make it possible to reuse Sugar Network in any Web browser in any Desktop Environment, i.e., not only from Sugar Shell;
* It might be easier to find potential Sugar contributors within Web developers rather than developers who know GTK.

It might sound a bit confusing to have local Web application, but this decision is based on:

* Local Web applications serve only one user and are much simpler than singular applications that are intended to serve multiple users simultaneously;
* It might be useful to design simple and clean code using existing Web technics like MVC;
* Thus, it will be easier for doers to learn, change, reimplement the new clients.

=== Personal server ===

This local application provides limited [[Platform_Team/Sugar_Network/API|API]] to get access to:

* Private data in user's home directory,
* Data accessible from removable devices like USB sticks or SD cards.

== Getting involved ==

{{:Sugar_Network/Feedback}}

== References ==

* An [http://wiki.laptop.org/go/Sneakernet OLPC wiki page] about the [[Wikipedia:Sneakernet|Sneakernet]].

Activities/TamTam

2011-12-19T20:52:44Z

RafaelOrtiz: /* Bundling from Sweets */

<noinclude>[[Category:Activities|Tam Tam]]</noinclude>
==Tam Tam developers' page==

===Overview===

TamTam is a suite of four music and sound related activities for the XO. TamTam is written in python with some C functions for speed-critical services. The audio engine for TamTam is Csound.

=== Build from sources ===

In Terminal activity, launch:

sudo yum install git csound-devel alsa-lib-devel python-devel make gcc-c++

Clone the sources and build binaries:

mkdir -p ~/Activities
git clone --depth 1 git://git.sugarlabs.org/tamtam/tamtam.git ~/Activities/tamtam
cd ~/Activities/tamtam/common/Util/Clooper
make

If make was successful, create symlinks to all TamTam activities:

cd ~/Activities/tamtam
./setup.py dev

== Bundling from Sweets ==

If you are using [http://wiki.sugarlabs.org/go/Platform_Team/Sweets Sweets] you can bundle your changes with

sweets bind sdk/sugar ./setup.py dist_xo

This can be done in the root of tamtam sources

==Resources==

* [[Tam Tam Resources]] - Learner resources
* [http://git.sugarlabs.org/projects/tamtam-branch Sources]
* Sugar Activity Library pages:
** [http://activities.sugarlabs.org/en-US/sugar/addon/4059 TamTamEdit]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4060 TamTamJam]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4061 TamTamMini]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4062 TamTamSynthLab]
* [http://wiki.laptop.org/go/TamTam TamTam on OLPC wiki]
* Trac tickets: [http://dev.laptop.org/query?component=tamtam-activity&col=id&col=summary&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority OLPC], [http://bugs.sugarlabs.org/query?component=TamTam&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs]

Activities/TamTam

2011-12-19T20:48:20Z

RafaelOrtiz: bundling from sweets

<noinclude>[[Category:Activities|Tam Tam]]</noinclude>
==Tam Tam developers' page==

===Overview===

TamTam is a suite of four music and sound related activities for the XO. TamTam is written in python with some C functions for speed-critical services. The audio engine for TamTam is Csound.

=== Build from sources ===

In Terminal activity, launch:

sudo yum install git csound-devel alsa-lib-devel python-devel make gcc-c++

Clone the sources and build binaries:

mkdir -p ~/Activities
git clone --depth 1 git://git.sugarlabs.org/tamtam/tamtam.git ~/Activities/tamtam
cd ~/Activities/tamtam/common/Util/Clooper
make

If make was successful, create symlinks to all TamTam activities:

cd ~/Activities/tamtam
./setup.py dev

== Bundling from Sweets ==

If you are using [[Sweets]] you can bundle your changes with

sweets bind sdk/sugar ./setup.py dist_xo

This can be done in the root of tamtam sources

==Resources==

* [[Tam Tam Resources]] - Learner resources
* [http://git.sugarlabs.org/projects/tamtam-branch Sources]
* Sugar Activity Library pages:
** [http://activities.sugarlabs.org/en-US/sugar/addon/4059 TamTamEdit]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4060 TamTamJam]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4061 TamTamMini]
** [http://activities.sugarlabs.org/en-US/sugar/addon/4062 TamTamSynthLab]
* [http://wiki.laptop.org/go/TamTam TamTam on OLPC wiki]
* Trac tickets: [http://dev.laptop.org/query?component=tamtam-activity&col=id&col=summary&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority OLPC], [http://bugs.sugarlabs.org/query?component=TamTam&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs]

Platform Team/Guide/Sweets Packaging

2011-12-06T22:42:31Z

RafaelOrtiz: typo

== Summary ==

This guide describes how to prepare software projects to be distributed via Sugar Labs' Packaging Management System, Sweets.

Make sure that you read the [[Platform_Team/Sweets|introduction page]] and [[Platform_Team/Guide/Sweets_Usage|Usage guide]]. To understand conceptual ideas, read the [[Platform_Team/Sweets/Glossary|Glossary]].

== Prepare the environment ==

Using the [[Platform_Team/Guide/Sweets_Usage#Installation|Usage guide]]'s instructions, install the Sweets. In addition, Sweets might be used from sources:

git clone git://git.sugarlabs.org/sdk/sweets.git
cd sweets
git submodule init
git submodule update
./sweets upgrade

The command {{Code|./sweets upgrade}} might require relogin from the X session to take into account the new PATH value.

== Recipe files ==

The recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like {{Code|.spec}} files in RPM. It is the cornerstone of Sweets, everything on the sweet project level depends on the recipe file. For activities, {{Code|activity/activity.info}}, an inherited recipe file name, is supported.

On a logical level, the entire Sweets infrastructure might be treated as a set of distribution bundles with sources that contain recipe files. Software projects are identified as Zero Install ''interfaces'' that contain information about which distribution bundle needs to be downloaded in order to launch a particular software version. That's not the full picture (there are binary bundles created based on sources), but it is useful for this topic's purpose. Read the [[#Development with Sweets|Development with Sweets]] section to learn about the available usage scenarios.

A recipe file is an [http://docs.python.org/library/configparser.html ini] format configuration file that might consist of several sections:

* One or more [[Platform_Team/Recipe_Specification#Use case sections|use case sections]].
* Optional [[Platform_Team/Recipe_Specification#Archive sections|archive sections]].
* Optional [[Platform_Team/Recipe_Specification#Auxiliary sections|auxiliary sections]].
* Optional {{Code|[DEFAULT]}} section with common options that are accessible from all other sections.

These files need to be placed in the root sources directory with names {{Code|sweets.recipe}} or {{Code|activity/activity.info}} for Sugar activities.

=== Writing recipes ===

In sources directory, create a recipe file, e.g., using {{Code|sweets init}} command. Recipe file should contain at least one [[Platform_Team/Recipe_Specification#Use case sections|use case]] section. There are several types of use case sections:

* ''Activity'' for Sugar activities,
* ''Application'' for stand alone applications,
* ''Library'' for libraries.

Make sure that all required options were set. The ''implement'' option has a special meaning, it is an [[Platform_Team/Sweets/Glossary#Implemented_interfaces|identifier]] of the sweet.

By default, the entirely sources directory will be packaged into sources tarball. In case if sources list needs to be restricted, add [[Platform_Team/Recipe_Specification#.5BBuild.5D|Source]] section with appropriate ''include'' and/or ''exclude'' options.

If the sweet needs to be built, add [[Platform_Team/Recipe_Specification#.5BBuild.5D|Build]] section.

If built files are platform dependent, add [[Platform_Team/Recipe_Specification#Archive_sections|Archive]] section with ''arch=any'' option.

=== Interfaces ===

The ''implement'', ''associate'' and ''requires'' (optionally) options contain [[Platform_Team/Sweets/Glossary#Short_form_for_sweet_interfaces|short interfaces]]. These values have two meanings:

* suffixes for final ''interface''s, e.g., {{Code|http://sweets.sugarlabs.org/''<value>''}},
* the name of project/package on [[Platform_Team/Open_Build_System|OBS]] that will be used to host released sweet.

In the 2nd case, the last slash separated part is a package, and the rest is a project, e.g., for ''sdk/sugar'', ''sdk'' is a project and ''sugar'' is a package in the ''sdk'' project.
It is possible to have interface values without slashes, in that case, project and package names are the same.

In the [[Platform_Team/Open_Build_System|OBS]], there is a special project named ''base''. This project contains sweets that all time will be represented only by native packages. In other words, if you need to make sure that your sweet needs to depend only on native packages, use dependencies from the ''base'' project.

The ''base'' project is also useful for [[Platform_Team/Sweets/Glossary#Associated_interfaces|associated]] interfaces set in ''associate'' recipe option. For example, if your sweet needs ''pygame=2'' dependency that is not yet widespread, create ''~user/pygame'' temporary sweet with ''2'' version only, and use ''~user/pygame'' as a dependency in your sweet. If ''base/pygame'' will be added as associated interface to the ''~user/pygame'', users that have ''>=2'' version in native packages will reuse them instead of ''~user/pygame'''s one.

See OBS [https://packages.sugarlabs.org/project/list_public projects] for all existed sweets.

=== Dependencies ===

Dependencies might be used in the ''requires'' and ''suggests'' options in recipes files to declare that the current sweet depends on another sweet/s.

The format of a dependency string is:

<interface> [(=|>=|<) <version>]

The ''interface'' value supports all interface [[#Interfaces|forms]]. The limited set of version conditions depends on Zero Install [http://0install.net/interface-spec.html specification] when the {{Code|<nowiki>=</nowiki>}} condition is a high level one and will be described in {{Code|<nowiki>>=</nowiki>}} and {{Code|<}} terms.

Dependencies may be optional. In that case, they need to be wrapped in square brackets. Optional dependencies will be used ''only'' if there is an [[Platform_Team/Sweets/Glossary#implementation|implementation]] to choose, otherwise they will be discarded without errors.

=== Stability status ===

Sweets should have stability status:

* ''stable'', final stable release,
* ''testing'', let people interested in testing try latest changes that are not yet stable,
* ''developer'', just a more extreme version of ''testing'',

This is a useful Zero Install feature that let developers share not yet stable version among the community. Since by default, only stable versions are being used, people, who are interested in helping developers in polishing not yet stable versions, need to explicitly choose not stable versions.

=== Glob patterns ===

The ''include'' and ''exclude'' options contain file patterns. A pattern could be of two types:

* doesn't contain ''/'' or ''**'' substrings, will be applied only to file names
* contains ''/'' or ''**'' substring, will be applied to the full file path (relative to the root), thus could affect several directory levels

Only these pattern symbols are allowed:

* ''*'' matches everything, except directory separator
* ''?'' matches any single character, except directory separator
* ''**'' matches everything, including directory separator

=== Examples ===

A list of recipe examples. Additionally, see {{Code|sugar*}} repositories in the [http://git.sugarlabs.org/sdk Gitorious sdk] repository, all of them are sweets.

'''Python activity'''

Python-based activity with standard Sugar Platform dependencies.

[Activity]
implement = cartoon-builder
name = Cartoon Builder
summary = Create your own cell-animation sequences
license = GPLv2+
homepage = http://wiki.sugarlabs.org/go/Activities/Cartoon_Builder

version = %(activity_version)s
stability = stable

icon = activity-cartoonbuilder
exec = sugar-activity activity.CartoonBuilderActivity

# Backwards compatibility of original activity.info options
bundle_id = com.ywwg.CartoonBuilderActivity
activity_version = 7

'''Python library'''

A python-based library that could be used as is, or as an activity dependency.

[Library]
implement = libjournal
name = libjournal
summary = Hight level library to create your own Journal-like activity
license = GPLv3+
homepage = http://wiki.sugarlabs.org/go/Activity_Team/Services/Journal
version = 1
stability = testing
requires = toolkit
binding = PYTHONPATH

'''C-based library'''

[DEFAULT]
depends = base/glib; base/gconf; base/libgee >= 0.5; base/gtk+ >= 2.12
base/pango >= 1.20; base/librsvg

[Library]
implement = polyol
name = polyol
summary = Intermediate level GObject based libraries for Sugar
description = Polyol is a set of libraries that are written in Vala.
Libraries are intended to provide high-level C API to basic Sugar
features including Gtk based user interface. Applications that are
linked against Polyol, interact with sugar processes
(like shell, datastore, etc.) via DBus.
license = LGPLv3+
homepage = http://wiki.sugarlabs.org/go/Activity_Team/Polyol

version = 1
stability = developer

binding = LD_LIBRARY_PATH lib
PKG_CONFIG_PATH lib/pkgconfig
VAPIDIR share/vala/vapi
requires = %(depends)s

[Archive]
arch = any

[Build]
requires = %(depends)s; pkg-config; cmake; make; gcc-c
configure = cmake -D CMAKE_INSTALL_PREFIX=%(PREFIX)s
-D PYTHON_SITEDIR=%(PREFIX)s/python
-D COMPONENTS="collab;ds;env;gui;shell;toolkit"
-D BINDING=python
-D CMAKE_C_FLAGS:STRING="%(CFLAGS)s"
.
make = make
install = make DESTDIR=%(DESTDIR)s install

== Releasing ==

In Sweets, releasing means uploading a sources tarball with a release (though, that [[#Stability_status|doesn't only mean]] stable versions) to the Sugar Labs [[Platform_Team/Open_Build_System|instance]] of the [http://openbuildservice.org/ Open Build Service] (OBS). Before releasing, make sure that you have a Sugar Labs [[Service/Account#Sugar_Labs_Central_Login|account]]. A login with password will be required the first time or when your cookie is missing.

Before releasing, make sure that your recipe conforms to the OBS [[Platform_Team/Open_Build_System/Policy|Policy]]. While releasing, sweet sources will be uploaded to an OBS project/package according to the [[#Interfaces|implement]] recipe option. If a particular project or package don't exist, they will be created (upon user's confirmation for project creation).

To initiate releasing, enter from the sweet sources directory:

sweets commit

The {{Code|sweets}} command will ask for a commit message, i.e., release notes. The same notes might be passed to {{Code|commit}} command via the {{Code|--message}} command-line argument.

If the releasing sweet is binary based, only the most recent stable version will be built on the OBS side, other versions will be built on the client side.

== Development with Sweets ==

Source bundles might be used on the client side not only indirectly, via {{Code|sweets}} command for example, but also explicitly. Sources might be bundled, emailed, etc. In this case, it is just like {{Code|.xo}} files. To make sources useful within Sweets, the local directory with sources might be employed in several ways:

* Applications might be launched from sources, {{Code|sweets ''<path-to-sources>''}};
* To reuse sources as dependencies for other sweets, the source directory needs to be registered in Sweets, {{Code|sweets checkout ''<path-to-sources>''}}; applications might be checked out as well.

Checking out will register a ''sweet'' in the local ''Sweets'' instance as a single ''implementation'' for the ''interfaces'' it ''implements''. This feature is especially useful for libraries, for example, if the sugar-toolkit sources, which implement the {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then, while running a {{Code|sdk/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of the {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}.

=== Sugar sweets ===

There are [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|sdk/sugar]] sweets that might be used as an example how to support sweets. Sweets Sugar sources are always rebased [http://git.sugarlabs.org/sdk forks] of upstream projects with added {{Code|sweets.recipe}} files and lightweight patches that make the original code useful via Sweets.

Checkout sources from:

* http://git.sugarlabs.org/sdk/sugar-base
* http://git.sugarlabs.org/sdk/sugar-toolkit
* http://git.sugarlabs.org/sdk/sugar-artwork
* http://git.sugarlabs.org/sdk/sugar

and see its {{Code|sweets.recipe}} files.

=== Developing activities ===

The traditional development related routine for activity sources is to run the {{Code|setup.py}} script located in the root activity directory. With Sweets, these routines might be accomplished with the {{Code|sweets}} command. Here is some background information:

* A downside of using Sweets is that running {{Code|setup.py}} requires being in the Sugar session (in order to have all the libraries that {{Code|setup.py}} injects);
* Sweets is designed to support multiple software versions at the same time. So to avoid having to login to different Sugar sessions for creating source tarballs, for example, it makes more sense to have a standalone utility;
* The {{Code|sweets}} command already contains development related functionality; it is useful to keep all development related functions in one utility.

Sweets support the following {{Code|setup.py}}'s commands:

* {{Code|build}}, build generated files, e.g., {{Code|locale/}} directory;
* {{Code|dist_xo}}, create a .xo with activity sources;
* {{Code|dist_source}}, create activity sources tarball;
* {{Code|genpot}}, generate the gettext pot file.

And doesn't support the following:

* {{Code|dev}} - seems to be a needlessly exaggerated function that creates a symbolic link in the {{Code|~/Activities}} directory to activity sources. The same might be done using the {{Code|ln -s}} command to avoid having derived functionality, or better, place sources directly in the {{Code|~/Activities}} directory;
* {{Code|fix_manifest}} - function creates {{Code|MANIFEST}} file. Not having this file is not a failure, and Sweets is designed to have include/exclude rules in recipe files instead;
* {{Code|install}} - function installs the activity to the root system. Sweets avoid, by design, any global changes during its regular behaviour.

As regular {{Code|sweets}}'s commands, these commands need to be executed from the activity directory (or in any of its sub-directories, not just in the root), or the path to activity sources might be specified after the command name, e.g.:

sweets build [PATH]

== Good practices ==

=== Devel packages ===

It is common practice in binary-based GNU/Linux distributions to use satellite devel packages to collect various build-time files like C headers or pkg-config files. In the Zero Install environment, this doesn't work, because every package is stored in a separate directory hierarchy, e.g., *.so symlinks, from devel package, will point to nothing, since all *.so.* files from the library package live in a separate directory.

Keep all build-time files in the sweet with runtime files.

=== Transparent behaviour ===

Library sweets that are associated with native packages ({{Code|base/*}} sweets), should use regular environment variables for binding, such as {{Code|LD_LIBRARY_PATH}}. The idea is that it should be possible to replace them with native packages transparently and avoid changes in sweets that use these libraries.

== Feedback ==

{{:Platform_Team/Sweets/Feedback}}

Platform Team/Usage Statistics

2011-11-30T03:03:38Z

RafaelOrtiz: /* Summary */

== Summary ==

Sugar usage statistics might be very useful from, e.g., an educational or research point of view. Statistics might be anonymous or personalized (by taking special efforts to keep information secure and locally used only for a particular deployment).

== Statistics ==

All types of statistics are identified by IDs in a dot separated hierarchy. This makes it possible to refer to the particular type or level of data.

* {{Code|shell}} Shell related stats.
** {{Code|shell.run}} Shell process is run.
** {{Code|shell.active}} Shell or activity window is active.
** {{Code|shell.collab}} Collaboration related stats in Shell.
*** {{Code|shell.collab.buddies}} Number of buddies in the Neighborhood view.
* {{Code|activity}} Activities related stats; specified only for the particular activity.
** {{Code|activity.run}} Activity is run.
** {{Code|activity.active}} Activity window is active.
** {{Code|activity.collab}} Collaboration related stats for activities.
*** {{Code|activity.collab.buddies}} Number of buddies activity is interacting with.
* {{Code|system}} System related stats.
** {{Code|system.uptime}} System uptime value.

== Implementation ==

=== Monitor ===

The usage statistics will be gathered by sniffing DBus and X11 messages in the [[Sugar_Server_Kit/sugar-client|sugar-client]] program launched with the {{Code|monitor}} command. The {{Code|sugar-client}} will stay in daemon mode, and send collected and filtered data to the [[Sugar_Server_Kit/sugar-server#collector|sugar-server]], or, will keep it for later collection in server-less environments.

=== Journal crawler ===

In addition to the realtime monitoring, it might be useful to collect some stats from the Journal. It should be possible to run this code on a client side, or, on school servers using Journal backups.

This feature was implemented in [http://wiki.paraguayeduca.org/index.php/Analisis_de_Uso_de_Actividades Paraguay], but is not being used right now.

=== Collector ===

=== Analyzer ===

== Resources ==

* [https://dev.laptop.org.au/issues/59 Australian request].

Activities/Classroom Broadcast

2011-11-29T15:23:15Z

RafaelOrtiz: /* Description */

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as [http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page TigerVNC] runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from

*http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install '''x11vnc''' enter the following in Terminal:

sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:

sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py

----

Must be fixed by v3 http://activities.sugarlabs.org/downloads/file/27762/classroombroadcast-3.xo --[[User:RafaelOrtiz|RafaelOrtiz]] 12:10, 28 November 2011 (EST)

----

* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Activities/Classroom Broadcast

2011-11-29T05:40:28Z

RafaelOrtiz: /* Installing */

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as TigerVNC runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from

*http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install '''x11vnc''' enter the following in Terminal:

sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:

sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py

----

Must be fixed by v3 http://activities.sugarlabs.org/downloads/file/27762/classroombroadcast-3.xo --[[User:RafaelOrtiz|RafaelOrtiz]] 12:10, 28 November 2011 (EST)

----

* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Activities/Classroom Broadcast

2011-11-29T05:36:17Z

RafaelOrtiz: /* Installing */

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as TigerVNC runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from

*http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install x11vnc enter the following in Terminal:
sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:
sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py

----

Must be fixed by v3 http://activities.sugarlabs.org/downloads/file/27762/classroombroadcast-3.xo --[[User:RafaelOrtiz|RafaelOrtiz]] 12:10, 28 November 2011 (EST)

----

* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Activities/Classroom Broadcast

2011-11-28T17:10:38Z

RafaelOrtiz: /* Known issues */

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as TigerVNC runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install x11vnc enter the following in Terminal:
sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:
sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py

----

Must be fixed by v3 http://activities.sugarlabs.org/downloads/file/27762/classroombroadcast-3.xo --[[User:RafaelOrtiz|RafaelOrtiz]] 12:10, 28 November 2011 (EST)

----

* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Activities/Classroom Broadcast

2011-11-28T15:09:38Z

RafaelOrtiz:

==Description==

ClassroomBroadcast transmits the screen of the 'server' laptop to the screens of a number of 'client' laptops. Typically the teacher's laptop would be the server and the students' laptops the clients. ClassroomBroadcast is a low cost alternative to using a data projector. ClassroomBroadcast runs on the server laptop and a VNC client such as TigerVNC runs on the client laptops.

==Installing==
Install ClassroomBroadcast on the 'server' laptop from http://activities.sugarlabs.org/addon/4507

ClassroomBroadcast also requires some additional software - x11vnc

To install x11vnc enter the following in Terminal:
sudo yum install x11vnc

Install a VNC client on all the client laptops, in Terminal enter:
sudo yum install vnc

==Running==
Check that all laptops are connected to the same network. Start ClassroomBroadcast on the server laptop. Press the button in the centre of the screen and note the IP address, eth0:, below the button.

[[File:Screenshot of "ClassRoomBroadcast Activity".png |450px]]

Start the VNC client on the client laptops by entering the following in Terminal
vncviewer

Enter the IP address eth0: from the server into the dialog box.

[[File:Screenshot of "VNC Viewer- Connection Details".png |450px]]

Alternatively you can specify the IP address in the command and skip the dialog box
vncviewer 10.1.1.4

Fullscreen mode allows the client to see the full screen but the client cannot quit till transmission stops

The fullscreen mode can be selected in options in the dialog box or specified from the commandline
vncviewer 10.1.1.4 -fullscreen

The screen of the sending laptop is mirrored on the receiving laptops. It takes a few seconds for the screens to update.

To stop transmitting, click the centre screen button in ClassroomBroadcast. ClassroomBroadcast can be closed like any regular Sugar Activity. When you are finished with the clients, you can close them by clicking the X in the screen upper right which returns you to Terminal. Terminal can then be closed like any regular Sugar Activity.

==Known issues==
With ClassRoomBroadcast V2 and TigerVNC Viewer 1.0.90

* Can only run one client, attempting to connect a second client gives 'end of stream'
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* Cannot disconnect and restart the client, error 111 connection refused
to fix add the option "-shared" at line 194 of classroombroadcast_activity.py
* The client gets seemingly random clipboard entries 'type clipping'
* Stopping the server first works OK, the client then quits. If you quit the client first then you have to click the server stop button twice to stop transmission
* The server cursor does not appear in the client laptops - fix, uncheck render cursor locally in TigerVNC options

Activities/GCompris

2011-11-25T14:44:13Z

RafaelOrtiz: /* Sharing support */

<noinclude>
{{TOCright}}
[[Category:Activities|GCompris]]
</noinclude>

== Overview ==

[http://gcompris.net/ Gcompris] with sugar support.

== Detailed Description ==

GCompris and GComprisAdministration activities create the same journal object with ''application/x-gcompris'' mimetype. So, when user creates journal object with GComprisAdministration activity, this object will be opened in GCompis activity by default. Use "Open with" context palette option to resume object in GComprisAdministration.

=== Sharing support ===

Teacher, in addition to GCompris Administration activity [http://gcompris.net/wiki/index.php?title=Manual#Administering_GCompris instructions]:
* Launch new GCompris Administration instance
* On tabs ''Classes/Users'' and ''Groups'', create users, groups and classes; these settings will be common for all GCompris Administration activity objects
* On tab ''Logins'', add groups of users that will be used for this GCompris Administration activity object
* On tab ''Activities'', setup list of activities for this GCompris Administration activity object
* Share activity
* On tab ''Reports'', see joined students' results

Students:
* Join shared by teacher GCompris object
* on startup, if resumed object is shared by teacher, GCompris will sync settings with teacher's object
* After completing GCompris activity, results will be sent to teacher and stored to student's object; later, this object could be opened by GCompris Administration activity to see these results

== Build from sources ==

Install dependencies, for Fedora they are:

sudo yum install gtk2-devel gstreamer-devel gstreamer-plugins-base-devel sqlite-devel librsvg2-devel libxml2-devel python-devel pygtk2-devel pycairo-devel gnucap gnuchess pkgconfig make gcc intltool glib2-devel GConf2-devel libgee-devel dbus-glib-devel pango-devel cmake gnet2-devel

Fetch sources:

mkdir -p ~/src/gcompris
cd ~/src/gcompris
wget http://download.sugarlabs.org/sources/external/polyol/polyol-1.2.tar.gz
tar xzpvf polyol-1.2.tar.gz
wget http://download.sugarlabs.org/sources/external/gcompris/gcompris-9.5.tar.gz
tar xzpvf gcompris-9.5.tar.gz

Build Polyol:

cd ~/src/gcompris/polyol-1.2
cmake -DCMAKE_INSTALL_PREFIX=$HOME/Activities/gcompris.activity && make && make install

Build GCompris:

cd ~/src/gcompris/gcompris-9.5
./configure PKG_CONFIG_PATH=$HOME/Activities/gcompris.activity/lib/pkgconfig --prefix=$HOME/Activities/gcompris.activity --enable-gnet --enable-sugar --enable-sqlite && make && make install

Link activity directory:

cd ~/Activities/gcompris.activity
ln -s share/sugar/activities/GCompris.activity/activity .

== Getting involved ==

* For non-Sugar related changes, go to [http://gcompris.net/-Contact,26- http://gcompris.net/].
* [http://bugs.sugarlabs.org/newticket?component=GCompris Report] on Sugar bugs.

== Resources ==

* [http://gcompris.net/ Home page]
* [http://git.sugarlabs.org/alsroot/gcompris Sugar patch sources]
* [http://activities.sugarlabs.org/en-US/sugar/addon/4313 Sugar Activity Library page]
* [http://wiki.laptop.org/go/GCompris GCompris on OLPC wiki]

Activities/Classroom Broadcast

2011-11-21T12:17:17Z

RafaelOrtiz: Created page with "TBD"

TBD

User:RafaelOrtiz

2011-11-21T11:33:11Z

RafaelOrtiz:

== Work ==

* http://dev.laptop.org/~rafael/
* http://wiki.laptop.org/go/Special:Contributions/RafaelOrtiz

== Contact ==

* http://wiki.laptop.org/go/User:RafaelOrtiz

== Notas ==

sweets bind sdk/sugar ./setup.py dist_xo

* Interes en OLPC sur acerca de sugar y niños con discapacidades..

preguntas: hay estudios al respecto, no solo utilizando sugar para trabajar con niños con discapacidades sensoriales sino tambien con discapacidades de aprendizaje.

Que acerca del trabajo con otro tipo de edades ? adult people ? older people ?.

== Activities ==

* http://openetherpad.org/AC-ActivityPack

== Honey proposals ==

*http://trisquel.pastebin.com/CPZ3H1zg

== Pootle ==
* Migrate to new version in the NEW vm.

== Recursos ==

* moo, cafepress, amazon.
* http://dev.olenepal.org/E-Paath-2/UNSTABLE/
* http://inclusion.semitagui.gov.co/index.php?title=Portada
* http://wiki.paraguayeduca.org/index.php/Portada
* Activityteam/sugar-lint
*
=== Programación web + desktop ===

* http://titaniumapp.com/
* http://www.salasaga.org/
* http://www.openlaszlo.org/
* http://ejohn.org/blog/processingjs/
* http://research.sun.com/projects/lively/

== TODOs ==

* Hacer un review del estado actual de las actividades.
* Turtle art Mas sensors.--investigar para thesis perifericos robots.
* Escribir pagina acerca de labyrinth
* gitorious@git.sugarlabs.org:turtleart/arduinosupport-clone.git
* gitorious@git.sugarlabs.org:turtleart/arduino-support.git

== Ideas ==

* Sugarizar calibre
* robots...minsky ideas.
* sugarize aslo
* web enviroment titanium.

== Links ==

*http://blogs.gnome.org/alexl/2010/11/23/gtk3-vs-html5/
*http://lively-kernel.org/
*http://zeitgeist-project.com/
*http://acko.net/blog/on-termkit
*http://blog.makezine.com/archive/2011/05/why-google-choosing-arduino-matters-and-the-end-of-made-for-ipod-tm.html
* http://hackasaurus.org/#participate
* http://vim.wikia.com/wiki/Remove_unwanted_spaces
* http://code.google.com/p/catroid/downloads/list
* http://www.kickstarter.com/projects/791396812/minibloq-graphical-programming-environment-for-ard
* http://www.ted.com/talks/marcin_jakubowski.html
* http://curveship.com/artmaking.html
* http://openclipart.org/
* https://dev.laptop.org.au/projects/xo-au/issues?query_id=6

== Contactos ==

*http://wiki.linux.org.pe/comunidades/peru
*http://listas.apesol.org/listinfo.cgi
*http://www.mochiladigitaltelmex.com.mx/olpc/index.php/Herramientas_pedagógicas (wiki educativo mexico)
*http://wiki-olpc.uca.edu.py/index.php/Portada wiki paraguay.
*http://alcob.com/new/alcom_alcob/alcom_alcob_disp.html

=Release mail proposal=

=[RELEASE] Terminal-#X=

notes if there are.

== Bundle ==

http://activities.sugarlabs.org/en-US/sugar/downloads/file/27397/clock-6.xo

== Source ==

http://download.sugarlabs.org/sources/honey/Clock/Clock-6.tar.bz2

== News ==

== Testing ==
(if necessary)

= Esta es una pagina de prueba =

--[[Usuario:RafaelOrtiz|RafaelOrtiz]] 00:54 18 nov 2011 (UTC)
[[Archivo:Ejemplo.jpg]]
<gallery>
Archivo:Ejemplo.jpg|Descripción1
Archivo:Ejemplo.jpg|Descripción2
</gallery>
#REDIRECT [[Nombre de la página destino]]
{| class="wikitable"
|-
! Texto de encabezado !! Texto de encabezado !! Texto de encabezado
|-
| Texto de celda || Texto de celda || Texto de celda
|-
| Texto de celda || Texto de celda || Texto de celda
|-
| Texto de celda || Texto de celda || Texto de celda

Dextrose/3/activites

2011-11-10T20:13:52Z

RafaelOrtiz: /* Introduction */

= Introduction =

TODO Tables; Ordering

''Note: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status: No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person:
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes Fixes not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person:
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer: Gonzalo
*DX person:
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person:
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person:
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Rafael Ortiz
*Notes: Used by AU deployment
*DX person: Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

== Testing ==

* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2011-11-10T15:23:28Z

RafaelOrtiz:

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

== Testing ==
* 1 and 2 priority activities are (and have to be) mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2011-09-28T22:47:22Z

RafaelOrtiz: /* Testing */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

*1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
*2. Activities are those that we work 20% as dextrose activities team (part of AC)
*3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

== Testing ==
* These are activities are mostly and thoughtfully tested under Dextrose OS builds.

Dextrose/3/activites

2011-09-28T05:11:48Z

RafaelOrtiz: init testing

User:RafaelOrtiz/Workshop/Pygame

2011-08-23T18:28:00Z

RafaelOrtiz: /* Temas */

=Workshop Pygame =

== '''Nombre''' Construyendo actividades con pygame ==

== '''Temas''' ==

*Introduccion que es sugar?, que es un actividad?
*Formas de hacer actividades.
*Pygame..por que Pygame?.
*Haciendo una actividad.
*Sugarizando.
**Empaquetando.
**Barras.(toolbars)

User:RafaelOrtiz/Workshop/Pygame

2011-08-23T18:27:01Z

RafaelOrtiz: /* Workshop Pygame = */

User:RafaelOrtiz/Workshop/Pygame

2011-08-23T18:26:23Z

RafaelOrtiz: Created page with "=Workshop Pygame == == Nombre Construyendo actividades con pygame == == Temas == *Introduccion que es sugar?, que es un actividad? *Formas de hacer actividades. *Pygame..por ..."

=Workshop Pygame ==

== Nombre Construyendo actividades con pygame ==

== Temas ==

*Introduccion que es sugar?, que es un actividad?
*Formas de hacer actividades.
*Pygame..por que Pygame?.
*Haciendo una actividad.
*Sugarizando.

Dextrose/3/activites

2011-08-22T19:54:09Z

RafaelOrtiz: /* org.laptop.Terminal Terminal */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
*State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T19:53:30Z

RafaelOrtiz: /* org.laptop.Log Log MIA */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log===
*Notes:
*Status: Active.
*Maintainer: gonzalo.
*DX person: dirakx
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T19:52:20Z

RafaelOrtiz: /* Calculator garycmartin */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log MIA ===
*Notes: pending some merge requests
Gonzalo is working to integrate -spyware patches and others
*Status:
*DX person:
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator===
*Notes:
*Maintainer:garycmartin
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T18:17:18Z

RafaelOrtiz: /* org.laptop.sugar.ReadActivity Read */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes:
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log MIA ===
*Notes: pending some merge requests
Gonzalo is working to integrate -spyware patches and others
*Status:
*DX person:
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator garycmartin===
*Notes:
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T18:16:42Z

RafaelOrtiz: /* org.laptop.WebActivity Browse */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing these problems and new enhancements
but crucial to deployments. All the development muscle will be focused in Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes: (creo que la idea es unirlo con getbooks etc) Gonzalo.
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log MIA ===
*Notes: pending some merge requests
Gonzalo is working to integrate -spyware patches and others
*Status:
*DX person:
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator garycmartin===
*Notes:
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T18:13:09Z

RafaelOrtiz: /* org.laptop.AbiWordActivity Write */

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Needs enhancements and new features.
*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing functionality problems and new enhancements
but crucial to deployments. All the development muscle will be focused in
Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes: (creo que la idea es unirlo con getbooks etc) Gonzalo.
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log MIA ===
*Notes: pending some merge requests
Gonzalo is working to integrate -spyware patches and others
*Status:
*DX person:
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator garycmartin===
*Notes:
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

Dextrose/3/activites

2011-08-22T18:11:28Z

RafaelOrtiz: adding activity

= Introduction =

TODO Tables; Ordering

''Notes: This activities list has names of people actually maintaining and names of dev support from Dextrose Activity team, it doesn't have all proper names of original developers.''

1. Activities are those that we work and support 80% of the time as dextrose activities team (part of AC)
2. Activities are those that we work 20% as dextrose activities team (part of AC)
3. These are activities that are left to community to work on

Originally Taken from:
http://activities.paraguayeduca.org/

== 1 Priority ==

===org.laptop.sugar.GetBooksActivity Get Books===
*Notes: Gonzalo is the maintainer.
*DX person: Icarito
*Status:No open bugs here.

===org.laptop.RecordActivity Record ===
*Actual Maintainer: Gonzalo, dsd
*Notes:Originally written by Erik Blankinship and Bakhtiar Mikhak.
*AC person:Icarito
*Status:
*Bugs: http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.AbiWordActivity Write ===
*Actual Maintainer: Gonzalo
*Notes:
*DX person: dirakx
*State: Fixing bug queue, narrowed down to enhancements
Needs enhancements and new features.

Repo not upstreamed in
gitorious@git.sugarlabs.org:~RafaelOrtiz/write/write-fixes.git

*Bugs:

=== org.laptop.WebActivity Browse ===
*Notes:
*DX person: dirakx - Icarito - Sascha
*Status: Cleaning bug queue
New versions fixed functionality problems
We should focus on fixing functionality problems and new enhancements
but crucial to deployments. All the development muscle will be focused in
Surf.

===org.laptop.sugar.ReadActivity Read===
*Notes: (creo que la idea es unirlo con getbooks etc) Gonzalo.
*DX person: Icarito
*Status: Needs bug fixing and new features.
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Record&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===org.laptop.Terminal Terminal===
*Notes: dirakx has commit access and maintainership permission by saya.
*DX person: dirakx
State: Fixing bug queue, new release needed.

===org.laptop.Chat ===
*Notes MIA, Fixes not upstreamed in TBD
gitorious@git.sugarlabs.org:~RafaelOrtiz/chat/chat-fixes.git
*AC person: Icarito
*State: developing new features, hippo dependency
*Bugs:http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Chat&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone

===TamTamMini TamTam ===
*Notes: alsroot, gonzalo dirakx: ''We are helping, but TamTam suite needs a maintainer''.
Originally written by Jean Piché and his students at the University of Montreal
*DX Person:
*State: Fixing bug queue, needs new release.

=== Pippy ===
*Notes: m_anish is principal MAINTAINER.
*Satus: Fixing bug queue, narrowing down to enhancements, need new release.
Changes in mainline
Needs packaging.
*DX person: dirakx

===Wikipedia-es===
*Notes:(Tadavia experimental) ''Needs testing but can be used.''
*Maintainer: Gonzalo.
*Status:
*Bugs:

===Edit ntt===
*Notes: has new toolbars in git but not released yet in a new bundle.
Doesn't have a trac component. []
Status
*DX person: Dirakx

== 2. Priority ==

===org.laptop.TurtleArtActivity Turtle BLocks===

*Notes: This is greatly maintained by walter, we can analyse the oportunity of making TA specific plugins for deployments.
*Maintainer: Walter

===org.laptop.Oficina Paint===
*Notes:
Oficina was originally written by students at Escola Politécnica of
Universidade de São Paulo
*Maintainer:Gonzalo
*DX person: icarito?
*Status:

===org.tuxpaint Tux Paint MIA ===
*Notes:
*DX person: Icarito
*Status:

=== vu.lux.olpc.Speak AC===
*Notes:
*Maintainer: dirakx
*Status: Fixing bugs, new enhancements.

===org.laptop.MeasureActivity Measure===
*Maintainer:Walter
*Notes:Would be nice to give a hand here.
*DX person: dirakx
*Status:
*Bugs:

===org.laptop.Log Log MIA ===
*Notes: pending some merge requests
Gonzalo is working to integrate -spyware patches and others
*Status:
*DX person:
*Bugs:

===net.gcompris GCompris===
*Notes
*DX person: icarito?
*Bugs:

===org.laptop.physics Physics garycmartin===
*Notes:
*DX person: icarito?
*Status:

===org.gnome.Labyrinth Labyrinth garycmartin ===
*Notes:
*Maintainer: garycmartin
*DX person:
*Status:

===vu.lux.olpc.Maze Maze AC dirakx===
*Notes:Enhancements needed.
*Maintainer: Rafael Ortiz

===Calculator garycmartin===
*Notes:
*DX person: Icarito
*Status: Actively maintained by Gary

===IRC===
*Notes: Has new toolbars now.
*Status: dirakx has commit access, Fran will do new releases.
DX person: dirakx

=== org.laptop.Memorize Memorize ===
*Maintainer:Walter/Gcmartin
*Notes:
*DX person:

=== Screencast ===
*Maintainer: Sebastian Silva
*Notes: Used by AU deployment
*DX person: Sebastian Silva, Rafael Ortiz

== 3.priority ==

===org.laptop.StopWatchActivity StopWatch (AC/ben/Dirakx Icarito)===
*Notes:Needs enhancements, new features.
*DX person:

===org.sugarlabs.AbacusActivity Abacus Walter===
*Notes:

===org.laptop.community.tetrismat Tetris Mat N/A===
*Notes:

===Moon Moon garycmartin===
*Notes: Actively maintained.

===org.laptop.Words Words (AC/Ben Dirakx-Icarito)===
*Notes: Enhancements new features.

===org.laptop.community.TypingTurtle Typing Turtle:===
*Notes:Gonzalo now has commit access, will do releases.

===org.laptop.community.Colors Colors N/A===
*Notes: Wade Brainerd <wadetb@gmail.com>
We need contact him. I have sent patches a few months ago (before the release of 10.3.1)
but there are not in git yet, and there are not a new release.

===org.laptop.ImageViewerActivity Image Viewer MIA?===
*Notes:Gonzalo has now commit access.

=== org.worldwideworkshop.olpc.FlipSticks Flip Sticks MIA===

===org.laptop.community.TurtleMachine Turtle Machine mulawa1===
New release is 21
mulawa is the dev/maintainer.

===com.laptop.Ruler Ruler Walter===
Originally written by Mitchell N. Charity

===com.jotaro.ImplodeActivity Implode joe@jotaro.com===

===org.laptop.community.Spirolaterals Spirolaterals muhawua===

===org.laptop.sugar.Jukebox Jukebox kushal/AC?===

===org.laptop.Arithmetic Arithmetic N/A===

===FotoToon FotoToon Gonzalo===

===org.sugarlabs.VisualMatchActivity Visual Match Walter===

===org.worldwideworkshop.PollBuilder Poll MIA?===

User:RafaelOrtiz

2011-07-07T19:47:26Z

RafaelOrtiz:

Activity Team/Git FAQ

2011-07-01T01:19:07Z

RafaelOrtiz: /* How do I apply a patch? */

<noinclude>{{TeamHeader|Activity Team}}</noinclude>
: '''[[Talk:Activity Team/Git FAQ | Post new questions here]]'''.
==Using gitorious (git.sugarlabs.org)==
=== Help! I suddenly can't connect to Gitorious! ===
:The [http://osuosl.org/ OSUOSL], which hosts Gitorious, has an aggressive IP blacklist policy. If you once were able to push but now cannot, send an email to support@osuosl.org requesting that your IP be removed from the blacklist.

To check if the problem is with your key, try:

ssh -v gitorious@git.sugarlabs.org

A successful ssh setup results in a normal response "Need SSH_ORIGINAL_COMMAND" then connection is closed.

=== How do I create an account on git.sugarlabs.org? ===

:[http://git.sugarlabs.org/users/new Register] using the link on the upper right menu on the Home Page.

===How do I migrate a project to git.sugarlabs.org? ===

:Please follow the [[Activity Team/How_to_migrate_from_OLPC|instructions here]] to first set up your project's entry in Gitorious.

=== How do I create a new project? ===

:First set up the project in gitorious as per above.

:Go to your project directory and type:
<nowiki>git init

git add .
git commit -a
git remote add origin gitorious@git.sugarlabs.org:[your project name]/mainline.git
git push origin master</nowiki>

:Hence forth, just use:
git commit
git push

:You can also use
git commit -a -m "I am the commit message"
:to avoid opening an editor.

=== How do I add an additional committer to my project? ===

:Click on the Repositories Tab of the project page in Gitorious. Click on "Mainline". A link will appear on the right-hand side of the page saying, "Add Committer".

=== How do I create a fork of an existing project? ===

:Click on the Repositories Tab of the project page in Gitorious. Click on "Mainline". A link will appear on the right-hand side of the page saying, "Clone repository".

:Note: if you (as maintainer) are making a clone to replace a corrupted mainline on your local machine, you'll need to:

git clone git://git.sugarlabs.org/yourproject/mainline.git

:and update [remote] section

git config remote.origin.url gitorious@git.sugarlabs.org:yourproject/mainline.git

----

:in the .git/config file, you may have to change:
[remote "origin"]
url = git://git.sugarlabs.org/yourproject/yourbranch.git

:to:
[remote "origin"]
url = gitorious@git.sugarlabs.org:yourproject/yourbranch.git

=== How do I request a merge? ===

:Click on the Repositories Tab of the project page in Gitorious. Click on "Mainline". A link will appear on the right-hand side of the page saying, "Request merge".

===What is the difference between a branch and a repository?===

When you make a clone of a project on gitorious, it creates a "repository". You can see the list of repositories associated with a project by clicking on the Repository Tab. Branches are clones within a repository (created with git branch and accessed through git checkout). Git merge commands refer to branches, not repositories, so in order to merge a repository back into mainline, you need to pull (fetch followed by merge) it as if it were a patch.

git merge [your repository name] # This won't work

git pull [git://git.sugarlabs.org/[your project name]/[your repository name].git master # This will work

===How do I select which branch I am working on?===

git checkout master

git checkout sucrose-0.84

===How do I merge changes from master into a branch?===

git checkout sucrose-0.84
git rebase master

===How do I push my branch to gitorious?===

Use <code>git push origin <your branch name></code>, e.g.,

git push origin sucrose-0.84

See [[Development_Team/Release#Branching]] for more details as to when and why you branch.

==Patches==

=== How do I generate a patch? ===

git diff > blah.patch
:or
diff -rup [old] [new]
:or
git format-patch HEAD^

It is preferable that you generate your patch from the root directory of your project.

=== How do I apply a patch? ===

First, take a look at what changes are in the patch. You can do this easily with '''git apply''' f.e:

git apply --stat sugar_fixes.patch

Note that this command does not apply the patch, but only shows you the stats about what it’ll do. After opening the patch file with your favorite editor, you can see what the actual changes are.

Next, you’re interested in how troublesome the patch is going to be. Git allows you to test the patch before you actually apply it.

git apply --check sugar_fixes.patch

If you don’t get any errors, the patch can be applied cleanly. Otherwise you may see what trouble you’ll run into. To apply the patch, we can use '''git am''' instead of '''git apply'''. The reason for this is that git am allows you to sign off an applied patch. This may be useful for later reference.

git am --signoff

Taken from: [http://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/]

==== Appying a patch from thunderbird ====
*Right click save as
* cat <save-as> | git am --signoff

=== How do I send a patch to a maintainer? ===

First, you may need to install git-mail:

sudo yum -y install git-email

An easy way to send a complete patch is to commit in git, then do:

git format-patch -s -1
git send-email --to <maintainer> --cc <mailing-list> <filename>

For example, you can do:

git send-email --to <maintainer> --subject=mail-subject 0003-service-name-deprecated.patch

git send-email --to <maintainer> --cc <mailing-list> --subject=new-patch --cover-letter --annotate 0001-*.patch

git send-email --to <maintainer> --cc <mailing-list> --subject=new-patch --cover-letter --annotate --no-validate 0001-*.patch

You can also generate a [[#How do I request a merge?|merge request]] on Gitorious from your forked repository to mainline.

=== How do I send a patch to the Sugar developers? ===

git send-email --to=sugar-devel@lists.sugarlabs.org 0001*.patch

==== How do I set up git-send-email? ====

1. Install git-email

2. Configure your ~/.gitconfig file
[user]
email = foo@sugarlabs.org
name = Foo Bar

[sendemail]
smtpserver = smtp.gmail.com
smtpserverport = 465
smtpuser = foo@sugarlabs.org
smtpencryption = ssl
suppresscc = author

3. In the directory where patch is present use:

git send-email HEAD^..HEAD --to "sugar-devel@lists.sugarlabs.org" patchname.patch

You can configure the destination address so you don't need to specify
it manually every time:

git config sendemail.to "sugar-devel <sugar-devel@lists.sugarlabs.org>"

You need to do this for each of the repositories you are working on (e.g. sugar + sugar-toolkit).

For more git send-email options please see ''man git send-email''

=== How do I amend a commit message? ===

If you have "dirty" history (i.e. other patches that are not in mainline
yet) please create a branch carrying only those two patches and push
that branch:

git checkout -b to-push origin/master
git cherry-pick <commit ID of first patch>
git commit --amend
(fix summary)
git cherry-pick <commit ID of second patch>
git commit --amend
(fix summary)
git push origin to-push:master

You can remove the branch afterwards:

git checkout master
git branch -d to-push

=== How do I revert a commit? ===

Again, best to do this on a branch as per [[#How do I amend a commit message?|above]]

Find the commit id and then:

git revert <commit ID>

=== As a maintainer, how do I merge a patch? ===

:git-pull does a combination of fetch and merge, so to merge a patch...

git pull git://git.sugarlabs.org/myproject/myproject-clone.git master

=== What is the community protocol for submitting patches? ===

# Introduce yourself to the community.
# Don't leave questions without a reply.
# Whenever you take a task that someone else was doing, mention it explicitly so others aren't concerned about wasting efforts.
# Ask when you don't understand.
# Answer other people's questions when you can.

==Internationalization work flow==

The i18n work flow involves an interplay between the Pootle server, where translations are maintained and gitorious, where the master POT files are updated. '''Note''': As a maintainer, you may update the .pot file associated with your project, but never update .po files. These are updated for you in the i18n work flow.

=== How do I get translations for my project? ===

# Use the gettext mechanism for your stings.
# Use <code>python setup.py genpot</code> to generate a .pot file for your project.
# Fill a ticket requesting that your POT file be added to Pootle. Assign the ticket to "Localization".
# Add User Pootle to the list of committers on your project.

=== How do I stay in sync with translations being pushed from the Pootle server? ===

:Periodically—in my experience, on Fridays—updates to the project .po files are pushed from the Localization team.

:Use <code> git-pull </code> to periodically pull these updates to the local copy of your project.

:Also, run <code>python setup.py fix_manifest</code> to update the .mo files after updating the .po files

:'''Note:''' After every major release, a new branch is created on the Pootle server, e.g., Fructose-0.82 and Fructose-0.84. The Localization team may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches.

=== How do my string changes get into Pootle? ===

Any changes to your project's .pot file are daily pulled into Pootle from git. All you have to do as a developer is make to regenerate your pot file whenever you make string changes.

setup.py genpot
git commit po/Myproject.pot -m "new strings"
git push

==Misc.==

=== What if my project has a binary blob? ===

:You may have to use the --force flag.

git push -fv

=== How do I update the Tag field in Gitorious? ===

git tag -m "Release 36" v36 HEAD
git push --tags

=== How do I list tags ? ===

git tag -l

=== How do I checkout specific tags? ===

git checkout <tag_name>

===How can I get commit access behind firewall?===

:If you are behind a firewall and need only ''Read-Only'' access to git.sugarlabs.org, you can use HTTP links, like
http://git.sugarlabs.org/git/<project>/mainline.git

:But if you need commit access, you'll have to set up an SSH proxy tunnel. One option is using [http://www.torproject.org/ Tor]. So, install all requirements:
* [http://www.torproject.org/ Tor] to make tunnel via Tor network,
* [http://www.meadowy.org/~gotoh/projects/connect/ connect] to let SSH use this tunnel.
:You don't need any special configs for this software (in case of Tor, if your distribution makes some smart pre-configurations, just remove /etc/tor/torrc).

:Setup your tunnel in SSH. Add the following lines to your ~/.ssh/config
Host git.sugarlabs.org
User gitorious
ProxyCommand /usr/bin/connect -S 127.0.0.1:9050 git.sugarlabs.org 22

:Then start [http://www.torproject.org/ Tor], you can just run it on behalf of your account
tor

:Then do the regular stuff you can do without any firewalls.

:''NOTE:'' If you use [http://www.torproject.org/ Tor] on a regular basis, please consider the possibility of [http://www.torproject.org/docs/tor-doc-relay.html.en helping] Tor by donating your bandwidth.

===Why are my commits not visible on git.sugarlabs.org event pages?===

Check that your email address on git.sugarlabs.org account page is the same like in [[Activity_Team/Git_Tutorial#Initialize_git_global_settings|global git settings]] or in local repository setting (if you set user.email once):
git config user.email

=== New activity maintainer walkthrough ===

Here's an IRC session recording the very first steps of new activity maintainer learning how to merge patches:

*:[[Activity_Team/Git_Activity_Maintainer_Walkthrough]]

[[Category:Activity Team]]
[[Category:FAQ]]