Sugar Labs - User contributions [en]

Sugar Labs DC/Online Activity Sharing and Publishing

2009-07-28T22:34:23Z

Jeddy: Removed several unnecessary links.

'''The Next Wave of Activity Sharing'''

Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar.

Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.

[[Image:Physics_Activity_Menu.png|400px|thumb|Example of the "Publish" option appearing in the Activity Palette]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.

Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to Scratch's would only work to expand and support the project as a whole.

Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.

Sugar needs a website comparable to Scratch's with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than Scratch's, as Scratch's website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).

Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.

The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.

Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage). They could find their uploads as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom with a web interface that would be deeply intertwined with Sugar and all of its activities, which would connect an entire generation and unite them in the spirit of learning.

Sugar Labs DC/Online Activity Sharing and Publishing

2009-07-28T22:31:40Z

Jeddy:

'''The Next Wave of Activity Sharing'''

Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar.

Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.

[[Image:Physics_Activity_Menu.png|400px|thumb|Example of the "Publish" option appearing in the Activity Palette]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.

Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to [http://www.scratch.mit.edu Scratch's] would only work to expand and support the project as a whole.

Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.

Sugar needs a website comparable to [http://www.scratch.mit.edu Scratch's] with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than [http://www.scratch.mit.edu Scratch's], as [http://www.scratch.mit.edu Scratch's] website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).

Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.

The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.

Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage). They could find their uploads as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom with a web interface that would be deeply intertwined with Sugar and all of its activities, which would connect an entire generation and unite them in the spirit of learning.

Sugar Labs DC/Online Activity Sharing and Publishing

2009-07-28T22:27:54Z

Jeddy:

'''The Next Wave of Activity Sharing'''

Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar.

Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.

[[Image:Physics_Activity_Menu.png|400px|thumb|Example of the "Publish" option appearing in the Activity Palette]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.

Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to [http://www.scratch.mit.edu Scratch's] would only work to expand and support the project as a whole.

Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.

Sugar needs a website comparable to [http://www.scratch.mit.edu Scratch's] with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than [http://www.scratch.mit.edu Scratch's], as [http://www.scratch.mit.edu Scratch's] website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).

Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.

The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.

Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage), and find their uploads, as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom
The end result of this project would be a web interface, deeply intertwined with Sugar and its activities, that would connect an entire generation and unite them in the spirit of learning.

Sugar Labs DC/Online Activity Sharing and Publishing

2009-07-28T22:26:26Z

Jeddy:

'''The Next Wave of Activity Sharing'''

Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar.

Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.

[[Image:Physics_Activity_Menu.png|400px|thumb|Example of Publish Option]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.

Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to [http://www.scratch.mit.edu Scratch's] would only work to expand and support the project as a whole.

Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.

Sugar needs a website comparable to [http://www.scratch.mit.edu Scratch's] with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than [http://www.scratch.mit.edu Scratch's], as [http://www.scratch.mit.edu Scratch's] website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).

Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.

The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.

Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage), and find their uploads, as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom
The end result of this project would be a web interface, deeply intertwined with Sugar and its activities, that would connect an entire generation and unite them in the spirit of learning.

File:Physics Activity Menu.png

2009-07-28T22:22:32Z

Jeddy:

Sugar Labs DC/Online Activity Sharing and Publishing

2009-07-28T22:21:56Z

Jeddy: Created page with ''''The Next Wave of Activity Sharing''' Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar. Scratch is a p…'

'''The Next Wave of Activity Sharing'''

Sugar Labs DC is interested in bringing the best elements of the [http://www.scratch.mit.edu Scratch] interface to Sugar.

Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.

In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.

Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to [http://www.scratch.mit.edu Scratch's] would only work to expand and support the project as a whole.

Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.

Sugar needs a website comparable to [http://www.scratch.mit.edu Scratch's] with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than [http://www.scratch.mit.edu Scratch's], as [http://www.scratch.mit.edu Scratch's] website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).

[[Image:Physics_Activity_Menu.png]] Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.

The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.

Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage), and find their uploads, as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom
The end result of this project would be a web interface, deeply intertwined with Sugar and its activities, that would connect an entire generation and unite them in the spirit of learning.

Sugar Labs DC

2009-07-28T20:45:10Z

Jeddy: Added link to Josh's Online Activity Sharing and Publishing Proposal.

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Sugar Labs DC|xbgColor=ffb673}}</noinclude>

'''Welcome to the Sugar Labs DC Project.'''

While Sugar Labs DC is in the early stages of formation, we already meet most
of the "necessary conditions" as laid out on the [[Local Labs]] page:

* A university connection as a local human resource

Sugar Labs DC will have the new [http://www.doe.virginia.gov/VDOE/Instruction/ct_academies/nga_grant/summaries/arlington.html Governor's Career and Technical Academy in Arlington] as an educational partner. Since the GCTAA is a joint project between [http://www.arlington.k12.va.us Arlington Public Schools] and [http://www.nvcc.edu Northern Virginia Community College], possibilities will be open for vertically integrated projects involving software written by students at GCTAA being used with APS elementary and middle school students.

* A local pilot user group from which to learn

Sugar Labs DC grew out of the [http://olpclearningclub.org OLPC Learning Club], so it is organically linked to a pilot user group.

* A local passion or sub-goal that provides a rational for the work

Faculty and students in Arlington Public Schools have an active 10 year involvement with the [http://python.org Python Programming Language] and Python community. The list of projects in which we have been involved include:
* [http://gvr.sf.net Guido van Robot]
* [http://openbookproject.net Open Book Project]
* [http://launchpad.net/gasp Graphics API for Students of Python (GASP)]
* [http://openbookproject.net/pybiblio Python Bibliotheca]
* [[Sugar Labs DC/Online Activity Sharing and Publishing]]

* Bi-directional communication with the global Sugar community and other Sugar Labs

Sugar Labs DC will be working directly with our partner project in Chalatenango, El Salvador, and we will always be looking for synergistic relationships with other communities around the globe.

* A sustainable and well-defined entrepreneurship model

Sugar Labs DC will function as a project of the OLPC Learning Club, and with the Learning Club will seek relationships and support from the many educational, scientific, and governmental organizations located in our capitol area.

* A program to reach out to local free-software community and local industry

Sugar Labs DC organizers are already active members of the local free-software community, and are particularly involved with the [http://dc.ubuntu-us.org DC Ubuntu LoCo Team].

[[Sugar Labs DC/Software Development Projects]]

[[Sugar Labs DC/Contacts|Team Members]]

[[Category:Local Lab]]
[[Category:Team]]
[[Category:Project]]