Changes

7. Documentation: There are a number of complementary efforts for documenting the Sugar API and the process for creating sugar activities: (1) a high-level functional design of Sugar (See http://wiki.laptop.org/go/Human_interface_guidelines); (2) a set of "how to's"; (3) a set of APIs generated from the actual code (extracted through pydocs); and (4) some basic startup guides.  

7. Documentation: There are a number of complementary efforts for documenting the Sugar API and the process for creating sugar activities: (1) a high-level functional design of Sugar (See http://wiki.laptop.org/go/Human_interface_guidelines); (2) a set of "how to's"; (3) a set of APIs generated from the actual code (extracted through pydocs); and (4) some basic startup guides.  

David Farning has spent the week cleaning up the Sugar application programming interface (API) reference documentation at api.sugarlabs.org. Code for the site is at [https://www.develer.com/gitweb/pub?p=users/dfarning/api.git;a=summary api.git] and a rough draft of an API tutorial can be found in the wiki ([[DevelopmentTeam/Tutorials/API_Documentation]]). David is soliciting modules from developers to add to the build_api.sh script, which he plans to run daily.

David Farning has spent the week cleaning up the Sugar application programming interface (API) reference documentation at api.sugarlabs.org. Code for the site is at [https://www.develer.com/gitweb/pub?p=users/dfarning/api.git;a=summary api.git] and a rough draft of an API tutorial can be found in the wiki ([[Documentation Team/API Documentation]]). David is soliciting modules from developers to add to the build_api.sh script, which he plans to run daily.

Faisal Anwar is writing a Sugar almanac to help new Sugar/Python developers. He is soliciting code samples and feedback. This week, he updated the section on how the basic activity creation tasks (Please see [http://wiki.laptop.org/go/Sugar.activity.activity Sugar.activity.activity]). In addition, he has written up some examples of basic datastore access. Additional documentation can be found at [http://wiki.laptop.org/go/Sugar-api-doc Sugar-api-doc].

Faisal Anwar is writing a Sugar almanac to help new Sugar/Python developers. He is soliciting code samples and feedback. This week, he updated the section on how the basic activity creation tasks (Please see [http://wiki.laptop.org/go/Sugar.activity.activity Sugar.activity.activity]). In addition, he has written up some examples of basic datastore access. Additional documentation can be found at [http://wiki.laptop.org/go/Sugar-api-doc Sugar-api-doc].

* dist-olpc4 - Fedora Rawhide tracker and buildroot experimentation (OLPC-specific changes needed to make Rawhide-based builds).

* dist-olpc4 - Fedora Rawhide tracker and buildroot experimentation (OLPC-specific changes needed to make Rawhide-based builds).

12. Feature freeze: An update on the status of the ongoing features can be found in the wiki ([[ReleaseTeam/Roadmap#New_features]]).

12. Feature freeze: An update on the status of the ongoing features can be found in the wiki ([[Development Team/Release/Roadmap#New_features]]).

13. Test plans: Michael Stone and the OLPC QA team are requesting that each release we get in the stable build is associated with a set of tests that they will perform to verify that things works as expected. It is proposed that it be mandatory to have a Trac item associated with each "news" in the git changelog and each Trac item would have a corresponding testcase.

13. Test plans: Michael Stone and the OLPC QA team are requesting that each release we get in the stable build is associated with a set of tests that they will perform to verify that things works as expected. It is proposed that it be mandatory to have a Trac item associated with each "news" in the git changelog and each Trac item would have a corresponding testcase.

In parallel, we'd like to start more formal user-testing in the field of some of the proposed Sugar feature changes. Walter had been in discussion with the deployment teams in Uruguay, Paraguay, and Peru about designating test environments. We'll likely use the new Frame behavior as a test case for testing.

In parallel, we'd like to start more formal user-testing in the field of some of the proposed Sugar feature changes. Walter had been in discussion with the deployment teams in Uruguay, Paraguay, and Peru about designating test environments. We'll likely use the new Frame behavior as a test case for testing.

14. Developers Meeting: Simon Schampijer reports that a summary of this week's developers meeting can be found here in the wiki ([[DevelopmentTeam/Meetings#Thursday_June_12_2008_-_17.00_.28UTC.29|12 June notes]]). Simon will be on a well-deserved holiday for the next two weeks; Tomeu will be hosting the weekly meeting on irc.

14. Developers Meeting: Simon Schampijer reports that a summary of this week's developers meeting can be found here in the wiki ([[Development Team/Meetings#Thursday_June_12_2008_-_17.00_.28UTC.29|12 June notes]]). Simon will be on a well-deserved holiday for the next two weeks; Tomeu will be hosting the weekly meeting on irc.

=== Sugar Labs ===

=== Sugar Labs ===

16. Self-organizing map (SOM): Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2008-June-07-13-som.jpg]]). The discussion seems to have been focused on features ("needs") and documentation.

16. Self-organizing map (SOM): Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2008-June-07-13-som.jpg]]). The discussion seems to have been focused on features ("needs") and documentation.