Changes

;Knowledge prerequisite: Strong background in Python, GTK3, and Atspi; some electronics background would also be useful.

;Knowledge prerequisite: Strong background in Python, GTK3, and Atspi; some electronics background would also be useful.

|-

|-

!valign=top | [[File:Bulletin-board.jpg|90px|left|thumb || valign=top | Bulletin Board || valign=top | Walter Bender ||align=left valign=top |

!valign=top | [[File:Bulletin-board.jpg|90px|left|thumb]] || valign=top | Bulletin Board || valign=top | Walter Bender ||align=left valign=top |

;Brief explanation:  

;Brief explanation: While it seems the prevailing notion of collaboration in the classroom is for the teacher to be able to a service such as VNC to share a desktop with a student, it is evident from computer-supported collaborative work outside of the classroom that such models provide little if any enhancements to productivity or learning. Our approach in Sugar has always been to allow our users to collaborate directly on tasks – be it writing a document together; sharing bookmarks while browsing; or sharing code snippets while programming. That said, often times, a large project involves multiple tools and multiple resources to be shared among a group. This project is to provide an uber-structure for collaboration – the Bulletin Board – where a group can share resources in a persistent manner as they work on a project together. One aspect it a shared, persistent "clipboard" of artifacts being used collectively within the project; another, illustrated on the left, is a chat channel that can be overlaid on top of activities to enable targeted discussions.

;Expected results:  

;Expected results: Two new Sugar toolkit services: a share, persistent clipboard; and a chat overlay onto any shared activity.

;Knowledge prerequisite:  

;Knowledge prerequisite: Strong background in Python and Gtk3

|}

|}