Changes

1. I am reminded of the power of IRC almost daily. Not only is it a place to ask a question, but it is a window into a wealth of discussion among domain experts trying to solve problems.  

1. I am reminded of the power of IRC almost daily. Not only is it a place to ask a question, but it is a window into a wealth of discussion among domain experts trying to solve problems.  

An analogy can be made to the "Engine Culture" described by David Cavallo in his PhD thesis: in rural Thailaind, engineers would work on motorcycle engines ''en plein air'', retrofiting them to solve the problem ''du jour''—a rice mill, a water pump, etc.—while the village children would gather around, taking in everything. IRC provides a similar opportunity. Hanging out in #sugar presents a great opportunity to gather around and take in everything.

An analogy can be made to the "Engine Culture" described by David Cavallo in his PhD thesis: in rural Thailand, engineers would work on motorcycle engines ''en plein air'', retrofitting them to solve the problem ''du jour''—a rice mill, a water pump, etc.—while the village children would gather around, taking in everything. IRC provides a similar opportunity. Hanging out in #sugar presents a great opportunity to gather around and take in everything.

We should experiment with ways to broaden participation with this learning opportunity. Some thoughts:

We should experiment with ways to broaden participation with this learning opportunity. Some thoughts:

3. It is great to see some of the core ideas such as Activities that underly Sugar become more mainstream. This will help us to broaden our community and our reach. C. Scott Ananian [http://cananian.livejournal.com/tag/google+wave blogged] about Google [http://www.waveprotocol.org/whitepapers/operational-transform Wave], a new collaboration model that has many goals in common with the Sugar collaboration model. Meanwhile, Benjamin Schwartz continues to make progress on his Google Summer of Code project, GroupThink, a completely decentralized, asynchronous text editing system.

3. It is great to see some of the core ideas such as Activities that underly Sugar become more mainstream. This will help us to broaden our community and our reach. C. Scott Ananian [http://cananian.livejournal.com/tag/google+wave blogged] about Google [http://www.waveprotocol.org/whitepapers/operational-transform Wave], a new collaboration model that has many goals in common with the Sugar collaboration model. Meanwhile, Benjamin Schwartz continues to make progress on his Google Summer of Code project, GroupThink, a completely decentralized, asynchronous text editing system.

4. Between interviews, Gary has been busy cranking out mockups for [[Marketing_Team/Boot_Logo#Sugar_Boot_Logo_Animations a new Sugar splash screen.]]

4. Between interviews, Gary has been busy cranking out mock ups for [[Marketing_Team/Boot_Logo#Sugar_Boot_Logo_Animations|a new Sugar splash screen.]]

5. All in a name: We have been have a discussion on the lists and in IRC about what to call the pending Sugar on a Stick release. The confusion lies in the gulf between the "stick", which will consist of Sugar Sucrose 0.84 and Fedora 11, both of which are essentially frozen, and the needs of a school to make a successful deployment, which includes requirements beyond the individual sticks themselves, e.g., a backup mechanism, documentation, etc. On the one hand, the developer have completed their work and are preparing to move on to the next phase: Sucrose 0.86 and Fedora 12. On the other hand, we don't want to set expectations that Sugar on a Stick is complete in regard to classroom settings, where we are only just beginning to do testing.

5. All in a name: We have been have a discussion on the lists and in IRC about what to call the pending Sugar on a Stick release. The confusion lies in the gulf between the "stick", which will consist of Sugar Sucrose 0.84 and Fedora 11, both of which are essentially frozen, and the needs of a school to make a successful deployment, which includes requirements beyond the individual sticks themselves, e.g., a backup mechanism, documentation, etc. On the one hand, the developer have completed their work and are preparing to move on to the next phase: Sucrose 0.86 and Fedora 12. On the other hand, we don't want to set expectations that Sugar on a Stick is complete in regard to classroom settings, where we are only just beginning to do testing.

One proposed solution to this communications dicotome is to use separate names for an individual stick and a collection of sticks used in a school setting. The best I've been able to come up with for the latter is Sugar Grove. Please share any thoughts you might have on naming with the SoaS and Marketing teams.

One proposed solution to this communications dichotomy is to use separate names for an individual stick and a collection of sticks used in a school setting. The best I've been able to come up with for the latter is Sugar Grove. Please share any thoughts you might have on naming with the SoaS and Marketing teams.

===Help Wanted===

===Help Wanted===

6. My plea for help this week is in regard to orphaned activities. There is [[Activity_Team/Activity_Status a list of activities with no active maintainer]] in the wiki. Adopting one or more of these activities would make a great summer project and be a practical way into Sugar development.

6. My plea for help this week is in regard to orphaned activities. There is [[Activity_Team/Activity_Status|a list of activities with no active maintainer]] in the wiki. Adopting one or more of these activities would make a great summer project and be a practical way into Sugar development.

===In the community===

===In the community===

===Sugar Labs ===

===Sugar Labs ===

13. Gary Martin has generated a SOM from the past week of discussion on the IAEP mailing list (Please see [[Image:2009-May-23-29-som.jpg]]).  

13. Gary Martin has generated a SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2009-May-23-29-som.jpg]]).  

=== Community News archive ===

=== Community News archive ===