<b>Some feedback:<br><br>Persistent storage overlay</b><br><a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users</a><br><div style="margin-left: 40px;">
6. Set the <i>Persistent Storage</i> slider to at least 160 MB (use more if you have a drive with more space);
<br></div><br>This confused me until I did some tests and discovered that if you don't do this then activities are not saved on the stick<br>When I did move the persistent storage slider to the end then after making the stick looked at properties the stick was full and I thought this might mean that you couldn't save (the opposite of what the words say)<br>
When the above says "to at least 160 MB (use more if you have a drive with more space)" this implies that there is some (unstated) reason for not moving the slider automatically to the end<br>Suggested rewording:<br>
<br>6. Set the <i>Persistent Storage</i> slider to the maximum so as to ensure that you can save your Sugar work onto the USB<br><br><br><b>Press release links</b><br>You need about 5 clicks to get from the press release link to strawberry<br>
Don't make users click unnecessarily - press release should go straight to<br><a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users</a><br>
<br><b>Some improvements</b><br>The current strawberry looks like a huge improvement on what was available a year ago (through Wolfgang) - thanks and congratulations to all involved. I have only done a few tests so far but the ability to save on the stick is a huge improvement. Also:<br>
<br>- when saving in turtle art a name your project box appears automatically<br>- the fast and slow icon feature in turtle art is great for learning<br>- also the TA feature that enables you to save the code as text logo (nice surprise)<br>
- I like the xo icon that that appears on the RHS persistently allowing for a quick shutdown from wherever you are (enhanced navigation)<br>- more interesting pippy examples with graphics on top is great<br>(I've only played with it for 5 minutes, no doubt will find many more, so thanks)<br>
<br><br><div class="gmail_quote">On Sat, Jun 27, 2009 at 1:05 AM, David Farning <span dir="ltr"><<a href="mailto:dfarning@sugarlabs.org">dfarning@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have started a thread for each individual ml; systems, devel, and<br>
marketing to collect ideas about what went right and what we can learn<br>
from the SoaS - Strawberry release.<br>
<br>
A debrief is not necessary about finding solutions, it is more like a<br>
semistructured brainstorm session 'get down on paper' ideas while they<br>
are fresh in people minds.<br>
<br>
If we do it correctly, the debrief can set the stage for the next<br>
iteration. Wash. Rinse, Repeat....<br>
<br>
Over all things went well. The biggest issue is how we define Sugar<br>
on a Stick the relationship between Sugar Labs and SoaS.<br>
<br>
To give a way the ending so it is transparent where I am coming from.<br>
<br>
Long term, SoaS should be distribution independent 'class of products'<br>
which conveys the idea of running the Sugar Learning Platform from a<br>
portable memory device.<br>
<br>
Short term, Sugar Labs, will need to selectively foster a specific<br>
release such as Sugar until it is viable for other communities and<br>
organizations to support the market.<br>
<br>
1. SoaS is fundamentally a distribution level project not a platform<br>
development project.<br>
2. SoaS is a larger movement that just SL. As such SL should focus<br>
on enabling the lager community to take SoaS and do what they want<br>
with it.<br>
3. SoaS is a great way to get Sugar into the hands of users. SL<br>
should promote SoaS however possible.<br>
4. SL should use clear language when talking about SoaS as generic<br>
idea and distribution specif implementations.<br>
<br>
These goals, need to be tempered with the reality that the open source<br>
development model depends a projects being 'valuable enough' for<br>
others to make the effort to use and improve the product.<br>
<br>
The tension is between SL 'making the market' yet not 'crowding out'<br>
potential contributors and partners.<br>
<br>
david<br>
_______________________________________________<br>
IAEP -- It's An Education Project (not a laptop project!)<br>
<a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
</blockquote></div><br><br>