Difference between revisions of "Sugar Labs/Current Events"
m (→Sugar Digest) |
|||
| Line 5: | Line 5: | ||
== Sugar Digest == | == Sugar Digest == | ||
| − | + | 1. Assessment is a topic that comes up again and again in discussions of Sugar. While there are several efforts under way to gather statistics about activity usage (See [[http://git.sugarlabs.org/desktop/stats 1], [[Platform_Team/Usage_Statistics|2]]] and [[http://git.sugarlabs.org/ds-analysis-scripts 3]], for example), most of those efforts are in service of everyone except the learner. In the spirit of "making learning visible", I modified an existing activity, [[Activities/Analyze_Journal|Analyze Journal]], written by Agustin Zubiaga Sanchez, in order give the Sugar user some feedback about their activity usage. Agustin had written the original activity to show free space in the Journal. I added two more views: one that displays a list of activities sorted by frequency of use; and one that shows statistics about block usage in Turtle Art activities. (The latter is based on a rubric developed jointly with Pacita Pena from Paraguayu Educa and Claudia Urrea from OLPC.) I am hoping that Analyze Journal and Portfolio (a previous effort to make learning visible) inspire the Sugar community to put more effort not just into gathering data for school administrators, but also in making reflection by the learners themselves part of the Sugar experience. | |
| − | + | One further note regarding Analyze Journal. I'd blogged recently about how youths who had grown up with Sugar were beginning to submit patches. In this case, the roles have reversed completely: I submitted the patch to Agustin. | |
| − | 2. | + | 2. In the keeping with spirit of the above discussion, [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/2a15fbc0f2269b1d61e5fa8ea723cb4848a8ee74 a new datastore metadata tag] has landed in Sugar 0.98. The "launch-times" tag is updated whenever an activity is launched. This will enable the learner to answer questions such as "how often have I used this activity?"; "do I use it in class, at home, or both?" Again, the goal is not to subsume the functionality potentially provided by [[[Platform_Team/Usage_Statistics|2]]], but to make the data available within Sugar itself more rich. |
| − | + | ||
| − | + | 3. There has been [http://lists.sugarlabs.org/archive/iaep/2012-October/015642.html a discussion on the IAEP list] about various strategies for using Turtle Blocks in support of robotics. The LEGO WeDo was discussed as one of several options currently available. It got me thinking that it may be time to finally add support for multiple WeDo devices. It is still beta, but please test [http://wiki.sugarlabs.org/images/0/00/Wedo_plugin_2.tar.gz the latest wedo_plugin]. In addition to supporting multiple devices, it also is a bit more robust in regard to plugging in and removing devices while the program is running. (In the first version of the code, the device had to be plugged in when Turtle Blocks launched. Now devices can be added and removed while Turtle Blocks is running.) | |
| − | |||
| − | |||
=== In the community === | === In the community === | ||
| − | + | 4. There are plans to hold the next [[Sugarcamp_SF_2012|OLPC SF summit in San Francisco]] the weekend of October 19-21. We are holding a Sugar Camp ''following'' the summit (Oct 22-24). | |
| − | |||
| − | |||
| − | |||
| − | |||
=== Sugar Labs === | === Sugar Labs === | ||
Revision as of 14:40, 6 October 2012
What's new
This page is updated each week (usually on Monday morning) with notes from the Sugar Labs community. (The digest is also sent to the community-news at sugarlabs.org list, blogged at walterbender.org, and archived here.) If you would like to contribute, please send email to walter at sugarlabs.org by the weekend. (Also visit planet.sugarlabs.org.)
Sugar Digest
1. Assessment is a topic that comes up again and again in discussions of Sugar. While there are several efforts under way to gather statistics about activity usage (See [1, 2] and [3], for example), most of those efforts are in service of everyone except the learner. In the spirit of "making learning visible", I modified an existing activity, Analyze Journal, written by Agustin Zubiaga Sanchez, in order give the Sugar user some feedback about their activity usage. Agustin had written the original activity to show free space in the Journal. I added two more views: one that displays a list of activities sorted by frequency of use; and one that shows statistics about block usage in Turtle Art activities. (The latter is based on a rubric developed jointly with Pacita Pena from Paraguayu Educa and Claudia Urrea from OLPC.) I am hoping that Analyze Journal and Portfolio (a previous effort to make learning visible) inspire the Sugar community to put more effort not just into gathering data for school administrators, but also in making reflection by the learners themselves part of the Sugar experience.
One further note regarding Analyze Journal. I'd blogged recently about how youths who had grown up with Sugar were beginning to submit patches. In this case, the roles have reversed completely: I submitted the patch to Agustin.
2. In the keeping with spirit of the above discussion, a new datastore metadata tag has landed in Sugar 0.98. The "launch-times" tag is updated whenever an activity is launched. This will enable the learner to answer questions such as "how often have I used this activity?"; "do I use it in class, at home, or both?" Again, the goal is not to subsume the functionality potentially provided by [[[Platform_Team/Usage_Statistics|2]]], but to make the data available within Sugar itself more rich.
3. There has been a discussion on the IAEP list about various strategies for using Turtle Blocks in support of robotics. The LEGO WeDo was discussed as one of several options currently available. It got me thinking that it may be time to finally add support for multiple WeDo devices. It is still beta, but please test the latest wedo_plugin. In addition to supporting multiple devices, it also is a bit more robust in regard to plugging in and removing devices while the program is running. (In the first version of the code, the device had to be plugged in when Turtle Blocks launched. Now devices can be added and removed while Turtle Blocks is running.)
In the community
4. There are plans to hold the next OLPC SF summit in San Francisco the weekend of October 19-21. We are holding a Sugar Camp following the summit (Oct 22-24).
Sugar Labs
Visit our planet for more updates about Sugar and Sugar deployments.
Community News archive
An archive of this digest is available.
Planet
The Sugar Labs Planet is found here.
