Changes

no edit summary
Line 5: Line 5:  
::: OK, good example of the confusion possible.  From [[Platform Team/Sweets]], the assumption is made that,
 
::: OK, good example of the confusion possible.  From [[Platform Team/Sweets]], the assumption is made that,
 
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
 
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
::: so Sweets seems to be aimed at those about to graduate to the software sharing stage of Sugar learning.  Do you think that this stage can be assumed for someone who has not launched or loaded Sugar before?  ('Someone', here, refers to a significant fraction of the the population of beginning Sugar learners.)  To this goal, significant stimulation efforts seem to be focused on providing malleable software at the Activity level, so learners can discover the gratification of creating new 'code' products.  Sweets seems a bit advanced from that early stage.  Clearly, a, or ''the'', goal is to lower the effort required for robust doer<->doer sharing. Seems like we need to advance by iteration with 'early adopters' and continue to eliminate all the 'hitches' and obstacles that discourage the vast majority of new users yet to become doers.  --[[User:FGrose|FGrose]] 22:49, 3 December 2011 (EST)
+
::: so Sweets seems to be aimed at those about to graduate to the software sharing stage of Sugar learning.  Do you think that this stage can be assumed for someone who has not launched or loaded Sugar before?  (''Someone'', here, refers to a significant fraction of the population of beginning Sugar learners.)  To this goal, significant stimulation efforts seem to be focused on providing malleable software at the Activity level, so learners can discover the gratification of creating new 'code' products.  Sweets seems a bit advanced from that early stage.  Clearly, a, or ''the'', goal is to lower the effort required for robust doer<->doer sharing. Seems like we need to advance by iteration with 'early adopters' and continue to eliminate all the 'hitches' and obstacles that discourage the vast majority of new users yet to become doers.  --[[User:FGrose|FGrose]] 22:49, 3 December 2011 (EST)
 
Could you look at the documentation with the eye toward drafting an introductory posting and page for new non-technical users?  If you could outline, or outright draft, an introduction, it would be a great service to us (and we need to exploit your 'newness' before it rapidly expires, if it hasn't already.) and much appreciated!  --[[User:FGrose|FGrose]] 21:23, 2 December 2011 (EST)
 
Could you look at the documentation with the eye toward drafting an introductory posting and page for new non-technical users?  If you could outline, or outright draft, an introduction, it would be a great service to us (and we need to exploit your 'newness' before it rapidly expires, if it hasn't already.) and much appreciated!  --[[User:FGrose|FGrose]] 21:23, 2 December 2011 (EST)