Changes

Jump to navigation Jump to search
Undo revision 99650 by KachachanC (talk)
Line 3: Line 3:  
===Sugar Digest===
 
===Sugar Digest===
   −
1. Oversight: We had a meeting of the acting oversight board (minutes are available [[Sugar_Labs/OversightBoard/Minutes#Friday_July_18_2008_-_17.00_.28UTC.29|here]]).  
+
1. Oversight: We had a meeting of the acting oversight board (minutes are available [[Oversight Board/Minutes#Friday_July_18_2008_-_17.00_.28UTC.29|here]]).  
    
2. Infrastructure: Ivan Krstić and Bernie Innocenti have been moving the Sugar Labs back-end infrastructure to a new server hosted at MIT. Please report any problems you may have encountered post-move (One artifact to note: its.an.education.project@tema.lo-res.org '''will not work'''. It will bounce e-mails. Please change your address book to iaep@lists.sugarlabs.org).
 
2. Infrastructure: Ivan Krstić and Bernie Innocenti have been moving the Sugar Labs back-end infrastructure to a new server hosted at MIT. Please report any problems you may have encountered post-move (One artifact to note: its.an.education.project@tema.lo-res.org '''will not work'''. It will bounce e-mails. Please change your address book to iaep@lists.sugarlabs.org).
   −
3. "Follow Through": Chris Leonard has created a wiki page ([[EducationTeam/Lesson Plan resources]]) to aggregate collections of lesson plans or curriculum development materials "posted in some dusty corners of the Internet"; they provide potentially useful modules of curricular content (constructionist and instructionist) that can either be adapted or at least serve as examples. Please contribute to the list with your own ideas and feedback on the postings.
+
3. "Follow Through": Chris Leonard has created a wiki page ([[Education Team/Lesson Plan resources]]) to aggregate collections of lesson plans or curriculum development materials "posted in some dusty corners of the Internet"; they provide potentially useful modules of curricular content (constructionist and instructionist) that can either be adapted or at least serve as examples. Please contribute to the list with your own ideas and feedback on the postings.
    
Another useful exercise would be to enhance these lesson plans through consideration of everything Sugar has to offer: journaling, collaboration, etc. A few detailed guides would go a long way towards opening the door to others, regardless of where the learning goals come from, generative or handed down from above.
 
Another useful exercise would be to enhance these lesson plans through consideration of everything Sugar has to offer: journaling, collaboration, etc. A few detailed guides would go a long way towards opening the door to others, regardless of where the learning goals come from, generative or handed down from above.
Line 54: Line 54:  
17. Speech synthesis: Hemant Goyals's Google Summer of Code project, "Integration of Speech Synthesis in Sugar Environment", is making great progress, according to Simon, the project supervisor. You can follow the progress at http://wiki.laptop.org/go/User:Hemant_goyal.
 
17. Speech synthesis: Hemant Goyals's Google Summer of Code project, "Integration of Speech Synthesis in Sugar Environment", is making great progress, according to Simon, the project supervisor. You can follow the progress at http://wiki.laptop.org/go/User:Hemant_goyal.
   −
18. Creative Commons: The addition of a Creative Commons (CC) licensing functionality in the Journal was discussed at this week's Sugar developers meeting (Please see [[DevelopmentTeam/Meetings#Creative_commons_licensing_functionality_in_the_journal|Creative Commons licensing functionality in the Journal]]).  
+
18. Creative Commons: The addition of a Creative Commons (CC) licensing functionality in the Journal was discussed at this week's Sugar developers meeting (Please see [[Development Team/Meetings#Creative_commons_licensing_functionality_in_the_journal|Creative Commons licensing functionality in the Journal]]).  
    
# Eben Eliason will make mock-up by August 15 ([http://dev.laptop.org/ticket/7551 Ticket 7551]);
 
# Eben Eliason will make mock-up by August 15 ([http://dev.laptop.org/ticket/7551 Ticket 7551]);
Line 75: Line 75:  
23. Activity updates: Eben Eliason has been working on tickets relevant to the pending 8.2 release, including new mockups for a software update system. Eben has been leading the discussion about activity versioning, which will probably not be resolved until release 9.1 Tomeu Vizoso added the ability to delete activities from the Home View. C. Scott Ananian worked an activity update control panel ([http://dev.laptop.org/ticket/4951 Ticket #4951]) inspired by OLPC Austria's XO-get activity and Bert Freudenberg's script. Scott requests that activity authors consider adding "update_url" fields to their activity.info files (Please see http://wiki.laptop.org/go/Activity_bundles). Brian Jordan wrote a script for pulling activities from git repositories and creating symlinks to them from the Activities folder; this enables you to "git pull" the newest version of an activity from a repository directly in a running Sugar environment (Please see [http://wiki.laptop.org/go/Activity_co-op Activity Coop]).
 
23. Activity updates: Eben Eliason has been working on tickets relevant to the pending 8.2 release, including new mockups for a software update system. Eben has been leading the discussion about activity versioning, which will probably not be resolved until release 9.1 Tomeu Vizoso added the ability to delete activities from the Home View. C. Scott Ananian worked an activity update control panel ([http://dev.laptop.org/ticket/4951 Ticket #4951]) inspired by OLPC Austria's XO-get activity and Bert Freudenberg's script. Scott requests that activity authors consider adding "update_url" fields to their activity.info files (Please see http://wiki.laptop.org/go/Activity_bundles). Brian Jordan wrote a script for pulling activities from git repositories and creating symlinks to them from the Activities folder; this enables you to "git pull" the newest version of an activity from a repository directly in a running Sugar environment (Please see [http://wiki.laptop.org/go/Activity_co-op Activity Coop]).
   −
24. Developer meetings: Upcoming meetings will have a fixed set of points that are discussed each meeting; additional topics that can be added by the attendees (Please see [[DevelopmentTeam/Meetings#The_Meeting_itself|The meeting itself]]).  
+
24. Developer meetings: Upcoming meetings will have a fixed set of points that are discussed each meeting; additional topics that can be added by the attendees (Please see [[Development Team/Meetings#The_Meeting_itself|The meeting itself]]).  
    
* updates from the past week (e.g. process changes);
 
* updates from the past week (e.g. process changes);
Line 82: Line 82:  
* introduction of new developers  
 
* introduction of new developers  
   −
Additional topics can be added by the developers during the week (Please see [[DevelopmentTeam/Meetings#How_to_add_topics|How to add topics]]). Those of you on the Sugar mailing list should expect to receive three meeting-related messages each week:
+
Additional topics can be added by the developers during the week (Please see [[Development Team/Meetings#How_to_add_topics|How to add topics]]). Those of you on the Sugar mailing list should expect to receive three meeting-related messages each week:
 
# Monday: reminder to add_topics
 
# Monday: reminder to add_topics
 
# Thursday: meeting reminder
 
# Thursday: meeting reminder
132

edits

Navigation menu