Changes

The Sugar-on-a-Stick team is very close to releasing Mirabelle, which is based on Fedora 13 and Sugar 0.88. It is an exciting release because it is both a great effort in terms of content and process. There has been a productive dialog between the packaging team, the developers, testers, and the user community; as a result, we are converging on a more sustainable process and we are better meeting the needs of our users. Many thanks, especially to Peter Robinson, Tom Gilliard, Caryl Bigenho, Mel Chua, James Cameron, Frederick Grose, and Sebastian Dziallas.

The Sugar-on-a-Stick team is very close to releasing Mirabelle, which is based on Fedora 13 and Sugar 0.88. It is an exciting release because it is both a great effort in terms of content and process. There has been a productive dialog between the packaging team, the developers, testers, and the user community; as a result, we are converging on a more sustainable process and we are better meeting the needs of our users. Many thanks, especially to Peter Robinson, Tom Gilliard, Caryl Bigenho, Mel Chua, James Cameron, Frederick Grose, and Sebastian Dziallas.

The Paraguay team is wrapping up their work on porting Fedora 11/Sugar 0.84 to the XO 1.0 hardware. This is important because it will allow deployments to migrate there installed base of machines to the same system being deployed on the XO 1.5 machines, making the overall support and maintenance problem more tractable. The team has also backported a number of bug fixes and features, such as 3G support, needed by deployments. It is a great example of downstream working with upstream.

The Paraguay team is wrapping up their work on porting Fedora 11/Sugar 0.84 to the XO 1.0 hardware. This is important because it will allow deployments to migrate their installed base of machines to the same system being deployed on the XO 1.5 machines, making the overall support and maintenance problem more tractable. The team has also backported a number of bug fixes and features, such as 3G support, needed by deployments. It is a great example of downstream working with upstream.

2. Dogi (Stefan Unterhauser), Adam Holt, and I were in Rochester this week for a series of events at RIT: the OLPC Users Group Meeting; the Dean's Lecture Series (I talked about why learning is so important; [http://www.ustream.tv/recorded/6561388 video]); and the Imagine RIT Innovation Festival. Our host was Stephen Jacobs. We spent some quality time with his students, whom are in project teams, developing two Sugar Activities: OVC (a video chat system being developed in collaboration with the National Institute for the Deaf), and Fortune Hunter, an adventure game geared towards 4th Grade mathematics. The great thing about the program at RIT is the way in which the student projects are being integrated into the global Sugar initative. I've asked Steve to share his "secret sauce" with other universities so that the model can spread.

2. Dogi (Stefan Unterhauser), Adam Holt, and I were in Rochester, New York this week for a series of events at RIT: the OLPC Users Group Meeting; the Dean's Lecture Series (I talked about why learning is so important; [http://www.ustream.tv/recorded/6561388 video]); and the Imagine RIT Innovation Festival. Our host was Stephen Jacobs. We spent some quality time with his students, whom are in project teams, developing two Sugar Activities: OVC (a video chat system being developed in collaboration with the National Institute for the Deaf), and Fortune Hunter, an adventure game geared towards 4th Grade mathematics. The great thing about the program at RIT is the way in which the student projects are being integrated into the global Sugar initative. I've asked Steve to share his "secret sauce" with other universities so that the model can spread.

One concrete outcome of the visit is the establishment of a Sugar "Story Team". Remy D of the RIT Storytelling Team has volunteered to lead the effort. Another tangible outcome is that three of the servers donated to Sugar Labs from the Wikipedia Foundation have a new home at RIT. Dogi worked with Steve's students to bring them up to speed on how to maintain the servers.

One concrete outcome of the visit is the establishment of a Sugar "Story Team". Remy D of the RIT Storytelling Team has volunteered to lead the effort. Another tangible outcome is that three of the servers donated to Sugar Labs from the Wikipedia Foundation have a new home at RIT. Dogi worked with Steve's students to bring them up to speed on how to maintain the servers.

3. The Sugar Oversight Board had an opportunity to meet face to face, along with about 10 community members whom happened to be in the Cambridge area. In addition to breaking bread together, we discovered that we had consensus regarding the on-going trademark debate. We'll be discussing and voting on the final wording of the policy next time we meet in IRC and will be summarizing (a) how the decision was made; (b) why it was made; (c) what alternatives were considered; (d) how it fits in with the Sugar Labs mission; (e) how it impacts the Sugar; and (f) how it impacts the Sugar community. Stay tuned.

3. The Sugar Oversight Board had an opportunity to meet face to face, along with about 10 community members whom happened to be in the Cambridge area. In addition to breaking bread together, we discovered that we had consensus regarding the on-going trademark debate. We'll be discussing and voting on the final wording of the policy next time we meet in IRC and will be summarizing (a) how the decision was made; (b) why it was made; (c) what alternatives were considered; (d) how it fits in with the Sugar Labs mission; (e) how it impacts Sugar; and (f) how it impacts the Sugar community. Stay tuned.

4. There has been a renewed and intense discussion about maintenance over the past few weeks. (The topic is an important one both to Sugar Labs and our downstream partners.) Our developer and release teams have been striving towards a set of well-documented procedures for making Sugar a project "with continuity, with an adequate progression in stability and new features and with a development process that gives them some control." You can follow the latest thread of the discussion [http://lists.sugarlabs.org/archive/iaep/2010-April/010740.html here].

4. There has been a renewed and intense discussion about maintenance over the past few weeks. (The topic is an important one both to Sugar Labs and our downstream partners.) Our developer and release teams have been striving towards a set of well-documented procedures for making Sugar a project "with continuity, with an adequate progression in stability and new features and with a development process that gives them some control." You can follow the latest thread of the discussion [http://lists.sugarlabs.org/archive/iaep/2010-April/010740.html here].